1 Reply Latest reply on Sep 6, 2002 5:50 PM by Dain Sundstrom

    dead lock and commit options

    Tim Fox Master

      I am using 3.0.2 with MVCSoft for persistence so effectively I am using BMP.

      I am constantly getting deadlock detected by the container, and it rolls back one of the transactions.

      The application was originally designed that different threads hardly ever concurrently access the same entities, in order to minimise deadlock.

      I have been informed that JBOSS ALWAYS exclusively locks any entities beans accessed in a transaction, irrespective of the commit option, and irrespective of whether the entities are changed.

      Can this be true??

      If so, it will explain my situation. Is there any known workaround for this, since this is crippling my project?

      Can i specify anywhere that I DO NOT WANT the entities to be exclusive locked.

      Please help!
      Thanks in adavance