1 Reply Latest reply on Feb 8, 2012 8:50 AM by Yaro Sheng

    HornetQ 2.2.2 Final - TransactionReaper::check timeout for TX

    Yaro Sheng Newbie



      I have Jboss 5.1.0 GA + HornetQ Final 2.2.2 installed.



      After receiving circa 800-850 requests server stops accepting them with the error (for each failed request):


      2012-02-06 12:09:17,559 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (Thread-7) [com.arjuna.ats.arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for TX ad76c5f:e249:4f2fb2c3:a18 in state  RUN

      2012-02-06 12:09:17,559 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (Thread-8) [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id ad76c5f:e249:4f2fb2c3:a18 invoked while multiple threads active within it.

      2012-02-06 12:09:17,559 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (Thread-8) [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action ad76c5f:e249:4f2fb2c3:a18 aborting with 1 threads active!

      2012-02-06 12:09:17,559 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] (Thread-8) [com.arjuna.ats.arjuna.coordinator.TransactionReaper_7] - TransactionReaper::doCancellations worker Thread[Thread-8,5,jboss] successfully canceled TX ad76c5f:e249:4f2fb2c3:a18


      In order to be able to accept any additional requests messages in JMS Queues should be removed.


      I tried to changed XA Resource Timeout parameter in Jboss Admin Console, but it didn't help even after server restart.


      In journal directory I have found server.lock file and found this discussion: https://community.jboss.org/thread/173277?tstart=0


      Can this issue be connected with the situation I have described above?


      Are there any other reasons why is it happening and why after cleaning the JMS Queues requests are accepted again?