1 Reply Latest reply on Oct 11, 2001 10:34 PM by Paul Fink

    transaction deadlock / trans-attribute settings

    Andreas Schouten Newbie


      Because of the duration of some transactions, we need to exclude read only access to EB from the current transaction.
      This is usely done with setting the trans-attribute to 'RequiresNew' for get methods.

      But this easy lead to deadlocks. If in a transaction two clints calls a EB, fist one a set method then second one a get, u get immediately a deadlock.

      Needed would be a trans-attribute which use the current transaction, if the bean is locked in this one and calls the method in a new otherwise.

      Is there a workaround for this problem or a better design pattern which avoid the problem?