I have a queue from which a JCA JMS consumer picks up the message, some EIP and XSLT processing is done after which it is stored in a database using a custom component. Under heavy load, this setup however tends to hang which means that messages are no longer processed but remain in the queue.
Both ServiceMix and ActiveMQ are deployed under JBoss. After some time I have the following warning in the log file: 2007-03-16 17:49:58,578 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=testbox/6879, BranchQual=, localId=6879] timed out. status=STATUS_ACTIVE If I try to shutdown the JMS consumer or the whole application server I get the following warning in the log file: 2007-03-16 18:15:54,630 INFO [STDOUT] ACtive Sessions = 10 This message repeats itself until the end of times and the only way to get out of this is to kill the process. It looks like transactions are not comitted for some reason and after a while timeout, however I cannot pin-point the exact problem. How can I prevent this hick-up from happening? How can I recover from this without killing the app server? Any suggestions? -- View this message in context: http://www.nabble.com/Transacted-synchronous-exchanges-tf3413934s12049.html#a9512683 Sent from the ServiceMix - User mailing list archive at Nabble.com.
