0 Replies Latest reply on Sep 19, 2001 6:15 PM by Jan


    Jan Newbie


      Bean A calls bean B but bean B fails to load properly and it causes Bean A to "hang."


      LOCKING-WAITING (TRANSACTION) for id Bean A ctx.hash 5435124 tx:TransactionImpl:XidImpl [FormatId=257, GlobalId=OPTIMUS//1, BranchQual=]


      I have 2 entity beans: department and employee. Department entity bean's ejbLoad calls findAllEmployees from the employee's home interface. The beans are then accessed which cause the employee beans to be loaded. However one of the employee fails to load which throw and exception and is caught. The exception caught is a javax.transaction.TransactionRolledbackException. Department entity bean's ejbLoad exited without complaining. However when I tried to access the department bean again the above Locking-Waiting error message is thrown. The server seems to just seat there after...for a long time.

      So I like to know what's happening and is there anything I can do to prevent the server from "hanging?"

      Thanks for your help.