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

    UserTransaction client error hangs jboss permanently

      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.

        • 1. Re: UserTransaction client error hangs jboss permanently
          vickyk

           

          "dietice" wrote:
          After the forced client disconnection, every statement executed inside the JBoss container waits indefinitely.

          I don't think it should be held for indefinte time, the in-doubt TX's should timeout after 5 minutes.
          How long do you wait before restarting the server?

          • 2. Re: UserTransaction client error hangs jboss permanently

            already tried the 5min and 15min timeouts (one was about statements, the other about transactions)

            what worries me most is that no other client request is served

            I've two warning in the log:

            11:28:14,353 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fa98:e92a:490ad7cf:16a invoked while multiple threads active within it.
            11:28:14,353 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fa98:e92a:490ad7cf:16a aborting with 1 threads active!
            


            • 3. Re: UserTransaction client error hangs jboss permanently
              jhalliday

              The transaction may well time out (the logs seem to indicate it does)... but it's unlikely to get disassociated from the AS thread. Remember JBossTS uses async rollback on a background thread for timeouts, whilst the ClientUserTransaction code was written for JBossTM. It probably needs reworking a bit to cope with its new reality.

              • 4. Re: UserTransaction client error hangs jboss permanently
                vickyk

                 

                "dietice" wrote:

                I've two warning in the log:
                11:28:14,353 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id -3f57fa98:e92a:490ad7cf:16a invoked while multiple threads active within it.
                11:28:14,353 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fa98:e92a:490ad7cf:16a aborting with 1 threads active!
                


                yes, these are the warnings that indicate the tx timeout had occurred.
                http://www.jboss.org/community/docs/DOC-12462



                • 5. Re: UserTransaction client error hangs jboss permanently

                   

                  "jhalliday" wrote:
                  It probably needs reworking a bit to cope with its new reality.


                  should I escalate this as bug report? Is there any ticket to watch regarding this task?