5 Replies Latest reply on Oct 31, 2008 7:07 AM by diet ice

    UserTransaction client error hangs jboss permanently

    diet ice Newbie

      Hi, I've the situation where a client starts a transaction using the remote usertransaction object.

      All the good tests cases works ok, but the failure cases give me some problems:

      killing the client after starting a transaction and without reaching a commit/rollback point, or any other form of client disconnection, causes the thread used to serve the client to be stuck with the transaction, and the transaction to never complete. After the forced client disconnection, every statement executed inside the JBoss container waits indefinitely.

      how do I avoid this issue? It's no good to have the jboss stopping to serve request to other client because one client failed during a transaction.