Hi wael_abdelwahab,
I started looking at this and thought it best to look in ems.log on one of my test servers and to see if I had the same errors. By coincidence I have come across what appears to be the same problem, but from looking in server.log rather than ems.log.
The same errors in my ems.log:
2015-10-30 09:16:51.630 ERROR: Transaction for non-existent consumer: 998 connID=2144 sessID=2580 {formatID=131075 gtrid_length=28 bqual_length=26 data=1-7f000101:c110:5632e4f3:23f7f000101:c110:5632e4f3:244}
2015-10-30 09:16:51.630 ERROR: Transaction for non-existent consumer: 999 connID=2144 sessID=2580 {formatID=131075 gtrid_length=28 bqual_length=26 data=1-7f000101:c110:5632e4f3:23f7f000101:c110:5632e4f3:244}
2015-10-30 09:16:51.630 ERROR: Transaction for non-existent consumer: 1000 connID=2144 sessID=2580 {formatID=131075 gtrid_length=28 bqual_length=26 data=1-7f000101:c110:5632e4f3:23f7f000101:c110:5632e4f3:244}
2015-10-30 09:16:51.631 ERROR: Error processing xa end - transaction marked ROLLBACKONLY, Exception. connID=2144 sessID=2580 {formatID=131075 gtrid_length=28 bqual_length=26 data=1-7f000101:c110:5632e4f3:23f7f000101:c110:5632e4f3:244}
2015-10-30 09:16:51.631 ERROR: Error processing xa prepare request, Transaction rollback. connID=2144 {formatID=131075 gtrid_length=28 bqual_length=26 data=1-7f000101:c110:5632e4f3:23f7f000101:c110:5632e4f3:244}
I then matched them to the following errors in server.log, which I had previously come across:
2015-10-30 09:16:51,636 WARN [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] XAResourceRecord.prepare - prepare failed with exception XAException.XAER_RMERR
2015-10-30 09:16:51,638 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_50] - Prepare phase of action 7f000101:c110:5632e4f3:23f received heuristic decision: TwoPhaseOutcome.HEURISTIC_HAZARD
2015-10-30 09:16:51,638 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_36] - BasicAction.End() - prepare phase of action-id 7f000101:c110:5632e4f3:23f failed.
2015-10-30 09:16:51,639 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_37] - Received heuristic: TwoPhaseOutcome.HEURISTIC_HAZARD .
2015-10-30 09:16:51,639 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_38] - Action Aborting
2015-10-30 09:16:51,834 ERROR [org.jboss.jms.asf.StdServerSession] failed to commit/rollback
javax.transaction.HeuristicMixedException
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1397)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:351)
at com.tibco.tibjms.TibjmsxSessionImp._submit(TibjmsxSessionImp.java:4001)
at com.tibco.tibjms.TibjmsxSessionImp._dispatchAsyncMessage(TibjmsxSessionImp.java:2220)
at com.tibco.tibjms.TibjmsxSessionImp._run(TibjmsxSessionImp.java:3477)
at com.tibco.tibjms.TibjmsxSessionImp.run(TibjmsxSessionImp.java:4680)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:761)
at java.lang.Thread.run(Thread.java:745)
I suspect that if you have similar messages in your server.log.20015-11-19 around 2015-11-19 12:58:56 then this will be fixed using document TEC614398:
Description:
Automatic Password reset results in a
"javax.transaction.HeuristicMixedException" exception while resetting
passwords.
Solution:
Do the following:
Navigate to the following directory: /JBOSS_HOME/server/default/deploy/jms
Open the jms-ds.xml and tibco-jms-ds.xml for editing.
Add the xml tag entries <track-connection-by-tx></track-connection-by-tx> in
<tx-connection-factory> in both files.
For example:
.
<tx-connection-factory>
....................................
<track-connection-by-tx></track-connection-by-tx>
.......................................
</tx-connection-factory>
Restart the JBoss service.
http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec614398.aspx
Note: This problem manifested itself with me by very occasionally having duplicate entries in Privileged Accounts -> Accounts -> Password History. Both entries would have the same password. This does not seem to affect the actual password change on the account.