We want certain business method calls to be synchronized.
Setting the transactional attribute to TRANSACTION_SERIALIZABLE on the session bean which starts the transaction doesn't help because the EJB server(weblogic) doesn't lock/synchronize the method call and leaves it to the database to do ther transaction management, which being oracle and implementing optimistic concurrency i.e snapshot instead of locking - let's both of them proceed and eventually both the method calls fail.
What would be the right solution for such problem ? Since we are not supposed to use "Synchronized" methods in EJB - should we implement our own locking ?
Sachin.
