Open MQ 4.3 "Bad transaction state transition"

Question

We have Open MQ 4.3 in remote, enhanced cluster. We are seeing ERRORs and WARNINGs in broker log file. They occur sporadically, once every couple hours or so. I think they might be related. Anyone have an idea what the problems may be?
1) "Bad transaction state transition"
[30/Jun/2009:00:48:12 EDT] ERROR com.sun.messaging.jmq.jmsserver.util.BrokerException: Bad transaction state transition. Cannot perform operation PREPARE_TRANSACTION(56) (XAFlag=null) on a transaction in state STARTED(1).: TUID=8284690576893811200 Xid=62726970706C303130302E6263627372692E6F72672C7365727665722C5032363137332C00E11C0000CD99242E62726970706C303130302E6263627372692E6F72672C7365727665722C503236313733:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Bad transaction state transition. Cannot perform operation PREPARE_TRANSACTION(56) (XAFlag=null) on a transaction in state STARTED(1).
at com.sun.messaging.jmq.jmsserver.data.TransactionState.nextState(TransactionState.java:440)
at com.sun.messaging.jmq.jmsserver.data.handlers.TransactionHandler.doPrepare(TransactionHandler.java:1625)
at com.sun.messaging.jmq.jmsserver.data.handlers.TransactionHandler.handle(TransactionHandler.java:551)
at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644)
at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170)
at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493)
at java.lang.Thread.run(Thread.java:595)
2) "ROLLBACK_TRANSACTION(48): Ignoring unknown XID"
[29/Jun/2009:22:54:34 EDT] WARNING ROLLBACK_TRANSACTION(48): Ignoring unknown XID=62726970706C303130302E6263627372692E6F72672C7365727665722C5032363137332C0006140000CD99242E62726970706C303130302E6263627372692E6F72672C7365727665722C503236313733 broker will notify the client
3) "Heartbeat timeout"
[29/Jun/2009:22:54:14 EDT] WARNING [B2122]: Heartbeat timeout from /192.168.106.192:32000 [brokerID=jmsnode_brippl0301, brokerSession=8155493556708599552] (seq#=7856, ts=1246330447089, interval=2, len=231) sender=/192.168.106.192:57964
Steve

Answer 1

Your question has also been posted to mq-interest alias with broker/appserver log files. The following is based on the log files:
1) "Bad transaction state transition"
The server.log you provided shows that right before this exception, there was appserver exception as below. It appears that something was wrong with the application/appserver state:
[#|2009-06-29T19:03:32.253-0400|WARNING|sun-appserver9.1|javax.enterprise.system.core.transaction|_ThreadID=22;_ThreadName=JMSJCA sync #0(queRouterRequest);Context=RouterJMS_ESB_R1_0032_PPMO_090626/queRouterRequest_svcBpRouterJMS_ejb;_RequestID=f92d8d20-1abb-4c0b-b6eb-cd205eabcd37;|JTS5041: The resource manager is doing work outside a global transaction
javax.transaction.xa.XAException
2) "ROLLBACK_TRANSACTION(48): Ignoring unknown XID"
This can be ignored. By looking at a couple of such WARNING messages in the broker log you provided
- The transaction was cleaned up on client connection closing and then the client reconnects, appserver attempts to rollback the old transaction.
3) "Heartbeat timeout"
This will be logged if the broker didn't receive heartbeat from the other broker for configured timeout period. This can happen occasionally due to network fluctuation. The heartbeat timeout values can be adjusted by broker "Failure Detection Properties"
http://docs.sun.com/app/docs/doc/820-6740/gguju?a=view