Weblogic throwing javax.transaction.HeuristicMixedException

Question

Hi,
Our application uses MQJMS binding and weblogic transaction manager to receive and send messages to and from external queue. We got "javax.transaction.HeuristicMixedException" when we restarted our application at some point of time. All the messages except two were successfully processed. These messages were stuck in database for processing, but were pushed to the MQ queue. Later on, the same messages got processed again. No other error/exception is logged
except below stack trace :
WSATGatewayRM_AdminServer_LUCM_TXN},NonXAResources={})],CoordinatorURL=AdminServer+10.237.252.77:27025+LUCM_TXN+t3+): javax.transaction.HeuristicMixedException: (BANCS_EAI_TXN_DataSource_LUCM_TXN, HeuristicHazard, ())
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:305)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:257)
at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:121)
at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:204)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
The above error looks very generic. How come the messages were sent to the Queue but not committed in the DB. Can someone help on this ?

Answer 1

This exception is thrown to report that a heuristic decision was made and that some relevant updates have been committed and others have been rolled back.
The reason for the rollback can be that some RuntimeException was thrown in processing the messages.
Have you also looked in the logging of the database or your MQ provider, maybe it was unable to give a commit to the weblogic transactionmanager, which
is controlling the XA transaction.