I am using JBoss 3.2.5 and have an MDB that updates some entity beans asynchronously when the user makes a change somewhere.
The MDB uses Bean managed Transactions but the entities that are being accessed in the transaction don't seem to be being locked.
If the (CMT) session bean sets a field on the entity, sends a message then completes processing and commits the transaction, the message arrives at the MDB before the transaction is committed, however, the onMessage method reads the field of the entity, but ends up with the value prior to the session bean setxxx.
The locking policy, commit option & InstanceCache are all set to JBOSS defaults.
I was under the impression that the getxxx method on the entity should be locked until the session bean's transaction is committed? Can someone explain? Is this a bug?
Post your question in a user forum not a developer forum.
Also what table type are you using MyISAM or InnoDB?