4 Replies Latest reply on May 31, 2005 9:31 AM by Ulf Schroeter

    Transaction Timeout

    Kevin Daly Newbie


      We are running JBoss 3.2.3 against a SQL Server database. We use the JMS Engine of JBoss quite extensively. JBoss is configured to use a PersistenceManager.

      We have one MDB configured as a singleton. This bean stop processing messages (usually at night) at times of relatively low server activity. An error

      2005-05-28 03:23:20,304 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=ANIMAL//13482941, BranchQual=] timed out. status=STATUS_ACTIVE

      appears in the logs, afterwhich no more messages are processed. To recover we have to re-start JBoss, it is not enough to restart the JMS Client (Publisher) which runs is a different process/Java App to JBoss.

      From what we can see, a message gets "stuck" in the JMSMessages table and is not being picked up by the Message Bean. When we restart JBoss we can see this message being processed. A message in the JMSMessage table is common to the behaviour, as is the WARN message. Another common theme is that the WARN message always appears 5 mins after the last message being processed. The previous message never shows any sign of error.

      Can anyone give pointers as where to debug this problem, we have seen similar errors in the Forums but nothing that helps shed any light on the issue ?

      We are considering updating JBoss versions in an effort to fix the problem, but are concerned that we may just be missing some config. option.