2 Replies Latest reply on Aug 26, 2005 3:20 AM by Joachim Van der Auwera

    Time out

    Vikrant Verma Newbie

      hi buddies,

      we are running some performance tests on the application which we have developed. we are using Stateless session beans, Jboss 4.x and jdk 1.5. During the performance tests, we are running 8 concurrent threads but are sporadically getting the following error:

      2005-08-25 11:54:58,907 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=srv-perceptor/36, BranchQual=, localId=36] timed out. status=STATUS_ACTIVE
      2005-08-25 11:54:58,907 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=srv-perceptor/34, BranchQual=, localId=34] timed out. status=STATUS_ACTIVE

      We have restarted the oracle server (our performance db) as I thought the problem is with the database locking but again got this error on running the 8 concurrent threads.

      Following attributes have been set for SLSBs:

      <session-type>Stateless</session-type>
      <transaction-type>Container</transaction-type>


      <container-transaction>

      <ejb-name>StationServiceFacade</ejb-name>
      <method-name>*</method-name>

      <trans-attribute>Required</trans-attribute>
      </container-transaction>

      I dont know where to debug this but can you please provide any inputs for the same. I owe a beer to the one who can help me solve this problem (world is so small that you never know when we meet :))

      - vikrant

        • 1. Re: Time out
          Vikrant Verma Newbie

          One more thing to add is that it is giving this error while executing a very simple query like following (related to the sequence service):

          UPDATE SEQUENCE
          SET SEQUENCEVALUE = (SEQUENCEVALUE + ?)
          WHERE SEQUENCENAME = ?

          • 2. Re: Time out
            Joachim Van der Auwera Expert

            Default tx timeout in jboss is 5 minutes. This can be configured in conf/jboss-service.xml under "TransactionManagerService".

            I would assume your SLSB does a lot of work and surpasses this 5 minute timeframe. You may have to either increase the tx timeout or split up your transaction.

            Joachim