3 Replies Latest reply on Apr 15, 2003 3:34 PM by lochenkinov

    [TxCapsule] timed out. status=STATUS_ACTIVE

    Erik Turesson Novice

      Hello!

      I am using jboss 3.06.
      Yesterday evening I received this error message on a server running my system.

      INFO | jvm 1 | 2003/04/01 22:25:15 | 22:25:15,015 WARN [TxCapsule] Transaction XidImpl [FormatId=257, GlobalId=james//449685, BranchQual=] timed out. status=STATUS_ACTIVE

      After that the system can not be reached.
      What does the error message mean and how to avoid it?

      /Erik

        • 1. Re: [TxCapsule] timed out. status=STATUS_ACTIVE
          lochenkinov Newbie

          any progress on this problem? i have the same thing happening.. so far i have tried changing transaction attributes to NotSupported, Required, and RequiresNew. my bean code has no transaction handling whatsoever, and i'm using the example oracle db pool xml file with my database user/password/url. the ajp13 threads build up until there are 65 or so (i think that's the limit i set) and then transaction timeouts start occurring.

          • 2. Re: [TxCapsule] timed out. status=STATUS_ACTIVE
            lochenkinov Newbie

            i am suspecting the mod_jk and/or ajp13 connector since i get socket write errors (pipe broken) while ajp connector is trying to finish the response. maybe somehow this is causing jboss to hold the transaction until the response is written. the response never gets written, so the transaction stays active until it times out. also, i never get the problem running direct to port 8080, only through the apache/ajp connector on 8009.

            • 3. Re: [TxCapsule] timed out. status=STATUS_ACTIVE
              lochenkinov Newbie

              (my response did not post the first time... trying again)

              i am suspecting the mod_jk and/or ajp13 connector since i get socket write errors (pipe broken) while ajp connector is trying to finish the response. maybe somehow this is causing jboss to hold the transaction until the response is written. the response never gets written, so the transaction stays active until it times out. also, i never get the problem running direct to port 8080, only through the apache/ajp connector on 8009.