Forums Register Login

Locking with Entity Beans

+Pie Number of slices to send: Send
Consider this sequence of events
Tx 1 : Loads Entiry A
TX 1: Update Entity A
Tx 2: Executes SQL Query to Read a row which is affected by Tx 1
Tx 1: commits

Should TX2 be locked out until TX1 is committed (it seems so) ? I am working in Websphere/DB2 environment with access intent policy wsPessimisticUpdateNoCollision. I am trying to find a way out of the locking situation. Would the behaviour be any different if instead of using direct SQL, we use EJB lookups?
If you were a tree, what sort of tree would you be? This tiny ad is a poop beast.
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 819 times.
Similar Threads
ejbActivate() and ejbPassivate() methods are called million times!!! :(
Hibernate Envers : How to delete entries from my audit table?
Need urgent help with Transaction
Session bean tranasactions with CMP
MDB and Tx
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 07:16:48.