From: danch <da...@nv...> - 2001-07-14 03:59:35
|
Anjan Rao wrote: > Hi all, > I have a doubt. It goes like this...I am using Oracle and entity beans on > JBoss. So, there are entity bean instances corresponding to records in > Oracle tables. Now, if some other application that also uses the same data > store deletes a few records, what happens to the entity bean instances for > the deleted records? > > AFAIK, there will be dirty reads if someone calls any find* methods, and > that the ejbstore and ejbremove will fail as the corresponding record is non > existent. Some of my front end applications using these entity beans might > get exceptions because of these dirty reads. Can there be any other issues > that i don't see? You want to use commit option C. That tells JBoss to only keep the entity bean instances active for the duration of a transaction. Also, if you're using CMP, set the select-for-update option to true in jaws.xml. That causes JBoss to use the 'SELECT ... FOR UPDATE' SQL syntax to lock all of the records so that they for sure won't get deleted while JBoss is in the middle of a transaction. See the manual online. |