This content has been marked as final.
Show 3 replies
-
1. Re: Help! Dirty read with commit option B on JBoss 3.2.0
adrian.brock Jun 2, 2004 5:30 AM (in response to realmaxim)Using 3.2.0
You would also be much better off using instance-per-transaction -
2. Re: Help! Dirty read with commit option B on JBoss 3.2.0
realmaxim Jun 2, 2004 6:04 AM (in response to realmaxim)I need single instance configuration and locking between transactions for entity beans and can't use instance-per-transaction configuration.
Anything more ? -
3. Re: Help! Dirty read with commit option B on JBoss 3.2.0
vadym Jun 1, 2005 10:35 PM (in response to realmaxim)I have a very similar problem only I use JBoss 3.2.7.
It looks like the second transaction gains access to the instance A during the first transaction where A supposed to be locked.
Why?
~Vadym