I'm having an XA_END error while trying to send a message from my banking application T24 to WMQ through my application server JBOSSError while starting JBoss serverError when trying to access my application in JBoss AS 7.1Errors while starting JBoss ServerHow to send message to jboss-7 from jboss-5Fail to deploy an aplication to JBoss7 while migrating an application from JBoss 6 to JBoss 7How to install WebSphere MQ resource adapter (wmq.jmsra.rar) in JBoss 6.2 EAP?Openshift: Trying to create java.websocket using JBoss Application ServerJBoss dropping connection after 30 min idle (Jboss XA Datasource with Oracle)Getting error when run the application in Jboss Cloud server 6.4.8How to run a Webapplication using Spring+EclipseLink jpa on Jboss v6
Could a Weapon of Mass Destruction, targeting only humans, be developed?
Meaning of じゃないんじゃない?
How do I tell the reader that my character is autistic in Fantasy?
What does grep -v "grep" mean and do?
How did Lefschetz do mathematics without hands?
Balanced parentheses using STL C++
Is it bad to describe a character long after their introduction?
Matrix decomposition
What exactly did Ant-Man see that made him say that their plan worked?
Picking balls from urns.
What does the phrase "building hopping chop" mean here?
Handling a player (unintentionally) stealing the spotlight
How can I add two boxes in minipages side by side?
Cast volatile array to non volatile array
Conjugate る-ending verbs into negative form
What could a reptilian race tell by candling their eggs?
How did installing this RPM create a file?
Why is Japan trying to have a better relationship with Iran?
What is "oversubscription" in Networking?
Using Raspberry Pi to flash its own SD card
Most important new papers in computational complexity
Boolean Difference with Offset?
Can two or more lightbeams (from a laser for example) have visible interference when they cross in mid-air?
Does a return economy-class seat between London and San Francisco release 5.28 t of CO2e?
I'm having an XA_END error while trying to send a message from my banking application T24 to WMQ through my application server JBOSS
Error while starting JBoss serverError when trying to access my application in JBoss AS 7.1Errors while starting JBoss ServerHow to send message to jboss-7 from jboss-5Fail to deploy an aplication to JBoss7 while migrating an application from JBoss 6 to JBoss 7How to install WebSphere MQ resource adapter (wmq.jmsra.rar) in JBoss 6.2 EAP?Openshift: Trying to create java.websocket using JBoss Application ServerJBoss dropping connection after 30 min idle (Jboss XA Datasource with Oracle)Getting error when run the application in Jboss Cloud server 6.4.8How to run a Webapplication using Spring+EclipseLink jpa on Jboss v6
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
0
I'm setting up the Banking application I use(T24) to send and receive messages from IBM MQ. I'm getting errors when I connect my application server(JBOSS 7) to MQ
I've tried altering the MDB's but to no avail.
This is a snippet from my Log file:
2019-03-22 17:00:17,269 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (default-threads - 13) wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.'.
2019-03-22 17:00:17,269 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default-threads - 24) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@213a8b6c[state=NORMAL managed connection=com.ibm.mq.connector.outbound.ManagedConnectionImpl@3db98551 connection handles=0 lastReturned=1553274017260 lastValidated=1553274017260 lastCheckedOut=1553274017260 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@2185ef44 mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@52753b07[pool=WMQ Connection Pool] xaResource=XAResourceWrapperImpl@518c200e[xaResource=com.ibm.mq.connector.xa.XARWrapper@67583e6a pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p910-L180709.TRIAL su=_QGElQYNUEeidSaRkJ_p2Kg pn=com.ibm.mq.connector/src/com/ibm/mq/connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/MQConnectionFactory] txSync=null]
2019-03-22 17:00:17,269 WARN [com.arjuna.ats.jta] (default-threads - 13) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffffc0a81701:-783f63b7:5c951441:40a3, node_name=1, branch_uid=0:ffffc0a81701:-783f63b7:5c951441:40b4, subordinatenodename=null, eis_name=java:jboss/jms/MQConnectionFactory > (XAResourceWrapperImpl@44eb1bdd[xaResource=com.ibm.mq.connector.xa.XARWrapper@c57055e pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p910-L180709.TRIAL su=_QGElQYNUEeidSaRkJ_p2Kg pn=com.ibm.mq.connector/src/com/ibm/mq/connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/MQConnectionFactory]) failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4'.
at com.ibm.mq.jmqi.JmqiXAResource.rollback(JmqiXAResource.java:874)
at com.ibm.mq.connector.xa.XARWrapper.rollback(XARWrapper.java:605)
at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.rollback(XAResourceWrapperImpl.java:196)
at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:369)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2999)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2978)
at com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1658)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127)
at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:134)
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.afterDelivery(MessageEndpointInvocationHandler.java:69)
at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.handle(AbstractInvocationHandler.java:60)
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:135)
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)
at com.temenos.tafj.mdb.TransactedMDB$$$endpoint1.afterDelivery(Unknown Source)
at com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkImpl.java:343)
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:849)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
jboss jboss7.x ibm-mq
edited Mar 25 at 14:39
JoshMc
5,8911 gold badge7 silver badges25 bronze badges
asked Mar 25 at 13:27
Chibuike ArnoldChibuike Arnold
1
add a comment |
0
I'm setting up the Banking application I use(T24) to send and receive messages from IBM MQ. I'm getting errors when I connect my application server(JBOSS 7) to MQ
I've tried altering the MDB's but to no avail.
This is a snippet from my Log file:
2019-03-22 17:00:17,269 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (default-threads - 13) wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.'.
2019-03-22 17:00:17,269 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default-threads - 24) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@213a8b6c[state=NORMAL managed connection=com.ibm.mq.connector.outbound.ManagedConnectionImpl@3db98551 connection handles=0 lastReturned=1553274017260 lastValidated=1553274017260 lastCheckedOut=1553274017260 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@2185ef44 mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@52753b07[pool=WMQ Connection Pool] xaResource=XAResourceWrapperImpl@518c200e[xaResource=com.ibm.mq.connector.xa.XARWrapper@67583e6a pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p910-L180709.TRIAL su=_QGElQYNUEeidSaRkJ_p2Kg pn=com.ibm.mq.connector/src/com/ibm/mq/connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/MQConnectionFactory] txSync=null]
2019-03-22 17:00:17,269 WARN [com.arjuna.ats.jta] (default-threads - 13) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffffc0a81701:-783f63b7:5c951441:40a3, node_name=1, branch_uid=0:ffffc0a81701:-783f63b7:5c951441:40b4, subordinatenodename=null, eis_name=java:jboss/jms/MQConnectionFactory > (XAResourceWrapperImpl@44eb1bdd[xaResource=com.ibm.mq.connector.xa.XARWrapper@c57055e pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p910-L180709.TRIAL su=_QGElQYNUEeidSaRkJ_p2Kg pn=com.ibm.mq.connector/src/com/ibm/mq/connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/MQConnectionFactory]) failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4'.
at com.ibm.mq.jmqi.JmqiXAResource.rollback(JmqiXAResource.java:874)
at com.ibm.mq.connector.xa.XARWrapper.rollback(XARWrapper.java:605)
at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.rollback(XAResourceWrapperImpl.java:196)
at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:369)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2999)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2978)
at com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1658)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127)
at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:134)
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.afterDelivery(MessageEndpointInvocationHandler.java:69)
at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.handle(AbstractInvocationHandler.java:60)
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:135)
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)
at com.temenos.tafj.mdb.TransactedMDB$$$endpoint1.afterDelivery(Unknown Source)
at com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkImpl.java:343)
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:849)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
jboss jboss7.x ibm-mq
edited Mar 25 at 14:39
JoshMc
5,8911 gold badge7 silver badges25 bronze badges
asked Mar 25 at 13:27
Chibuike ArnoldChibuike Arnold
1
add a comment |
0
0
0
I'm setting up the Banking application I use(T24) to send and receive messages from IBM MQ. I'm getting errors when I connect my application server(JBOSS 7) to MQ
I've tried altering the MDB's but to no avail.
This is a snippet from my Log file:
2019-03-22 17:00:17,269 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (default-threads - 13) wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.'.
2019-03-22 17:00:17,269 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default-threads - 24) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@213a8b6c[state=NORMAL managed connection=com.ibm.mq.connector.outbound.ManagedConnectionImpl@3db98551 connection handles=0 lastReturned=1553274017260 lastValidated=1553274017260 lastCheckedOut=1553274017260 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@2185ef44 mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@52753b07[pool=WMQ Connection Pool] xaResource=XAResourceWrapperImpl@518c200e[xaResource=com.ibm.mq.connector.xa.XARWrapper@67583e6a pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p910-L180709.TRIAL su=_QGElQYNUEeidSaRkJ_p2Kg pn=com.ibm.mq.connector/src/com/ibm/mq/connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/MQConnectionFactory] txSync=null]
2019-03-22 17:00:17,269 WARN [com.arjuna.ats.jta] (default-threads - 13) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffffc0a81701:-783f63b7:5c951441:40a3, node_name=1, branch_uid=0:ffffc0a81701:-783f63b7:5c951441:40b4, subordinatenodename=null, eis_name=java:jboss/jms/MQConnectionFactory > (XAResourceWrapperImpl@44eb1bdd[xaResource=com.ibm.mq.connector.xa.XARWrapper@c57055e pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p910-L180709.TRIAL su=_QGElQYNUEeidSaRkJ_p2Kg pn=com.ibm.mq.connector/src/com/ibm/mq/connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/MQConnectionFactory]) failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4'.
at com.ibm.mq.jmqi.JmqiXAResource.rollback(JmqiXAResource.java:874)
at com.ibm.mq.connector.xa.XARWrapper.rollback(XARWrapper.java:605)
at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.rollback(XAResourceWrapperImpl.java:196)
at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:369)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2999)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2978)
at com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1658)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127)
at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:134)
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.afterDelivery(MessageEndpointInvocationHandler.java:69)
at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.handle(AbstractInvocationHandler.java:60)
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:135)
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)
at com.temenos.tafj.mdb.TransactedMDB$$$endpoint1.afterDelivery(Unknown Source)
at com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkImpl.java:343)
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:849)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
jboss jboss7.x ibm-mq
edited Mar 25 at 14:39
JoshMc
5,8911 gold badge7 silver badges25 bronze badges
asked Mar 25 at 13:27
Chibuike ArnoldChibuike Arnold
1
I'm setting up the Banking application I use(T24) to send and receive messages from IBM MQ. I'm getting errors when I connect my application server(JBOSS 7) to MQ
I've tried altering the MDB's but to no avail.
This is a snippet from my Log file:
2019-03-22 17:00:17,269 INFO [org.jboss.as.connector.deployers.RaXmlDeployer] (default-threads - 13) wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.'.
2019-03-22 17:00:17,269 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default-threads - 24) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@213a8b6c[state=NORMAL managed connection=com.ibm.mq.connector.outbound.ManagedConnectionImpl@3db98551 connection handles=0 lastReturned=1553274017260 lastValidated=1553274017260 lastCheckedOut=1553274017260 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@2185ef44 mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@52753b07[pool=WMQ Connection Pool] xaResource=XAResourceWrapperImpl@518c200e[xaResource=com.ibm.mq.connector.xa.XARWrapper@67583e6a pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p910-L180709.TRIAL su=_QGElQYNUEeidSaRkJ_p2Kg pn=com.ibm.mq.connector/src/com/ibm/mq/connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/MQConnectionFactory] txSync=null]
2019-03-22 17:00:17,269 WARN [com.arjuna.ats.jta] (default-threads - 13) ARJUNA016045: attempted rollback of < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffffc0a81701:-783f63b7:5c951441:40a3, node_name=1, branch_uid=0:ffffc0a81701:-783f63b7:5c951441:40b4, subordinatenodename=null, eis_name=java:jboss/jms/MQConnectionFactory > (XAResourceWrapperImpl@44eb1bdd[xaResource=com.ibm.mq.connector.xa.XARWrapper@c57055e pad=false overrideRmValue=null productName=IBM MQ productVersion=@(#) MQMBID sn=p910-L180709.TRIAL su=_QGElQYNUEeidSaRkJ_p2Kg pn=com.ibm.mq.connector/src/com/ibm/mq/connector/outbound/ManagedConnectionMetaDataImpl.java jndiName=java:jboss/jms/MQConnectionFactory]) failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4'.
at com.ibm.mq.jmqi.JmqiXAResource.rollback(JmqiXAResource.java:874)
at com.ibm.mq.connector.xa.XARWrapper.rollback(XARWrapper.java:605)
at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.rollback(XAResourceWrapperImpl.java:196)
at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:369)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2999)
at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2978)
at com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1658)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:127)
at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1282)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:143)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:134)
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.afterDelivery(MessageEndpointInvocationHandler.java:69)
at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.handle(AbstractInvocationHandler.java:60)
at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:135)
at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)
at com.temenos.tafj.mdb.TransactedMDB$$$endpoint1.afterDelivery(Unknown Source)
at com.ibm.mq.connector.inbound.AbstractWorkImpl.run(AbstractWorkImpl.java:343)
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223)
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:849)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
jboss jboss7.x ibm-mq
jboss jboss7.x ibm-mq
edited Mar 25 at 14:39
JoshMc
5,8911 gold badge7 silver badges25 bronze badges
asked Mar 25 at 13:27
Chibuike ArnoldChibuike Arnold
1
edited Mar 25 at 14:39
JoshMc
5,8911 gold badge7 silver badges25 bronze badges
asked Mar 25 at 13:27
Chibuike ArnoldChibuike Arnold
1
edited Mar 25 at 14:39
JoshMc
5,8911 gold badge7 silver badges25 bronze badges
edited Mar 25 at 14:39
JoshMc
5,8911 gold badge7 silver badges25 bronze badges
edited Mar 25 at 14:39
JoshMc
5,8911 gold badge7 silver badges25 bronze badges
5,8911 gold badge7 silver badges25 bronze badges
asked Mar 25 at 13:27
Chibuike ArnoldChibuike Arnold
1
asked Mar 25 at 13:27
Chibuike ArnoldChibuike Arnold
1
asked Mar 25 at 13:27
Chibuike ArnoldChibuike Arnold
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
0
That error can be safely ignored.
XAER_NOTA is a valid return from xa_rollback()
The XA specification indicates that "[a]n RM can also unilaterally roll back and forget a branch any time except after a successful prepare"
answered Mar 25 at 14:43
Doug GroveDoug Grove
4062 silver badges5 bronze badges
Thanks for the reply Doug. Although, its difficult to ignore because my JBOSS keeps on looping with the same error, and my log file fills up to more than 1 Gigabyte due to the incessant looping. Also, Any message I manually put into one of my queues, gets moved to my Back-Out queue immediately jboss loads and connects with MQ. My Banking software also doesn't successfully send any message to MQ while JBOSS has connected. It's all strange to me because I just started using MQ and thought that after successfully connecting it to JBOSS and my application through those MDB setups, It'd work.
– Chibuike Arnold
Mar 25 at 18:12
Looking at the stack trace, you can see the 'afterDelivery()'. This means that the MDBs 'onMessage()' has returned. The transaction is then being rolled back. This means that the transaction was either marked in the code as being rollback only, or some exception occurred that caused the transaction to be rolled back.
– Doug Grove
Mar 27 at 12:40
Thanks for the reply Doug. I really appreciate it. A few more questions please. Any idea what could be causing the Transaction to rollback? I've been searching online, but I've not really been able to find out what causes the errors:1(xa_end has failed with error code '100') 2.(ARJUNA016045: attempted rollback of <*****failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4') 3.(IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener*****)
– Chibuike Arnold
Mar 28 at 12:38
The "Destroying connection that could not be successfully matched" is actually due to a bug in the IBM JCA client code. The transaction match check on the JMS session wasn't working correctly. I think that this was fixed in 8.0.0.4, but then popped up again in 8.0.0.10.
– Doug Grove
Mar 29 at 13:18
Wow. How about this error: wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.' That seems to be the genesis of the problem.
– Chibuike Arnold
Mar 30 at 17:45
|
show 1 more comment
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55338902%2fim-having-an-xa-end-error-while-trying-to-send-a-message-from-my-banking-applic%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
That error can be safely ignored.
XAER_NOTA is a valid return from xa_rollback()
The XA specification indicates that "[a]n RM can also unilaterally roll back and forget a branch any time except after a successful prepare"
answered Mar 25 at 14:43
Doug GroveDoug Grove
4062 silver badges5 bronze badges
Thanks for the reply Doug. Although, its difficult to ignore because my JBOSS keeps on looping with the same error, and my log file fills up to more than 1 Gigabyte due to the incessant looping. Also, Any message I manually put into one of my queues, gets moved to my Back-Out queue immediately jboss loads and connects with MQ. My Banking software also doesn't successfully send any message to MQ while JBOSS has connected. It's all strange to me because I just started using MQ and thought that after successfully connecting it to JBOSS and my application through those MDB setups, It'd work.
– Chibuike Arnold
Mar 25 at 18:12
Looking at the stack trace, you can see the 'afterDelivery()'. This means that the MDBs 'onMessage()' has returned. The transaction is then being rolled back. This means that the transaction was either marked in the code as being rollback only, or some exception occurred that caused the transaction to be rolled back.
– Doug Grove
Mar 27 at 12:40
Thanks for the reply Doug. I really appreciate it. A few more questions please. Any idea what could be causing the Transaction to rollback? I've been searching online, but I've not really been able to find out what causes the errors:1(xa_end has failed with error code '100') 2.(ARJUNA016045: attempted rollback of <*****failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4') 3.(IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener*****)
– Chibuike Arnold
Mar 28 at 12:38
The "Destroying connection that could not be successfully matched" is actually due to a bug in the IBM JCA client code. The transaction match check on the JMS session wasn't working correctly. I think that this was fixed in 8.0.0.4, but then popped up again in 8.0.0.10.
– Doug Grove
Mar 29 at 13:18
Wow. How about this error: wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.' That seems to be the genesis of the problem.
– Chibuike Arnold
Mar 30 at 17:45
|
show 1 more comment
0
That error can be safely ignored.
XAER_NOTA is a valid return from xa_rollback()
The XA specification indicates that "[a]n RM can also unilaterally roll back and forget a branch any time except after a successful prepare"
answered Mar 25 at 14:43
Doug GroveDoug Grove
4062 silver badges5 bronze badges
Thanks for the reply Doug. Although, its difficult to ignore because my JBOSS keeps on looping with the same error, and my log file fills up to more than 1 Gigabyte due to the incessant looping. Also, Any message I manually put into one of my queues, gets moved to my Back-Out queue immediately jboss loads and connects with MQ. My Banking software also doesn't successfully send any message to MQ while JBOSS has connected. It's all strange to me because I just started using MQ and thought that after successfully connecting it to JBOSS and my application through those MDB setups, It'd work.
– Chibuike Arnold
Mar 25 at 18:12
Looking at the stack trace, you can see the 'afterDelivery()'. This means that the MDBs 'onMessage()' has returned. The transaction is then being rolled back. This means that the transaction was either marked in the code as being rollback only, or some exception occurred that caused the transaction to be rolled back.
– Doug Grove
Mar 27 at 12:40
Thanks for the reply Doug. I really appreciate it. A few more questions please. Any idea what could be causing the Transaction to rollback? I've been searching online, but I've not really been able to find out what causes the errors:1(xa_end has failed with error code '100') 2.(ARJUNA016045: attempted rollback of <*****failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4') 3.(IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener*****)
– Chibuike Arnold
Mar 28 at 12:38
The "Destroying connection that could not be successfully matched" is actually due to a bug in the IBM JCA client code. The transaction match check on the JMS session wasn't working correctly. I think that this was fixed in 8.0.0.4, but then popped up again in 8.0.0.10.
– Doug Grove
Mar 29 at 13:18
Wow. How about this error: wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.' That seems to be the genesis of the problem.
– Chibuike Arnold
Mar 30 at 17:45
|
show 1 more comment
0
0
0
That error can be safely ignored.
XAER_NOTA is a valid return from xa_rollback()
The XA specification indicates that "[a]n RM can also unilaterally roll back and forget a branch any time except after a successful prepare"
answered Mar 25 at 14:43
Doug GroveDoug Grove
4062 silver badges5 bronze badges
That error can be safely ignored.
XAER_NOTA is a valid return from xa_rollback()
The XA specification indicates that "[a]n RM can also unilaterally roll back and forget a branch any time except after a successful prepare"
answered Mar 25 at 14:43
Doug GroveDoug Grove
4062 silver badges5 bronze badges
answered Mar 25 at 14:43
Doug GroveDoug Grove
4062 silver badges5 bronze badges
answered Mar 25 at 14:43
Doug GroveDoug Grove
4062 silver badges5 bronze badges
answered Mar 25 at 14:43
Doug GroveDoug Grove
4062 silver badges5 bronze badges
4062 silver badges5 bronze badges
Thanks for the reply Doug. Although, its difficult to ignore because my JBOSS keeps on looping with the same error, and my log file fills up to more than 1 Gigabyte due to the incessant looping. Also, Any message I manually put into one of my queues, gets moved to my Back-Out queue immediately jboss loads and connects with MQ. My Banking software also doesn't successfully send any message to MQ while JBOSS has connected. It's all strange to me because I just started using MQ and thought that after successfully connecting it to JBOSS and my application through those MDB setups, It'd work.
– Chibuike Arnold
Mar 25 at 18:12
Looking at the stack trace, you can see the 'afterDelivery()'. This means that the MDBs 'onMessage()' has returned. The transaction is then being rolled back. This means that the transaction was either marked in the code as being rollback only, or some exception occurred that caused the transaction to be rolled back.
– Doug Grove
Mar 27 at 12:40
Thanks for the reply Doug. I really appreciate it. A few more questions please. Any idea what could be causing the Transaction to rollback? I've been searching online, but I've not really been able to find out what causes the errors:1(xa_end has failed with error code '100') 2.(ARJUNA016045: attempted rollback of <*****failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4') 3.(IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener*****)
– Chibuike Arnold
Mar 28 at 12:38
The "Destroying connection that could not be successfully matched" is actually due to a bug in the IBM JCA client code. The transaction match check on the JMS session wasn't working correctly. I think that this was fixed in 8.0.0.4, but then popped up again in 8.0.0.10.
– Doug Grove
Mar 29 at 13:18
Wow. How about this error: wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.' That seems to be the genesis of the problem.
– Chibuike Arnold
Mar 30 at 17:45
|
show 1 more comment
Thanks for the reply Doug. Although, its difficult to ignore because my JBOSS keeps on looping with the same error, and my log file fills up to more than 1 Gigabyte due to the incessant looping. Also, Any message I manually put into one of my queues, gets moved to my Back-Out queue immediately jboss loads and connects with MQ. My Banking software also doesn't successfully send any message to MQ while JBOSS has connected. It's all strange to me because I just started using MQ and thought that after successfully connecting it to JBOSS and my application through those MDB setups, It'd work.
– Chibuike Arnold
Mar 25 at 18:12
Looking at the stack trace, you can see the 'afterDelivery()'. This means that the MDBs 'onMessage()' has returned. The transaction is then being rolled back. This means that the transaction was either marked in the code as being rollback only, or some exception occurred that caused the transaction to be rolled back.
– Doug Grove
Mar 27 at 12:40
Thanks for the reply Doug. I really appreciate it. A few more questions please. Any idea what could be causing the Transaction to rollback? I've been searching online, but I've not really been able to find out what causes the errors:1(xa_end has failed with error code '100') 2.(ARJUNA016045: attempted rollback of <*****failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4') 3.(IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener*****)
– Chibuike Arnold
Mar 28 at 12:38
The "Destroying connection that could not be successfully matched" is actually due to a bug in the IBM JCA client code. The transaction match check on the JMS session wasn't working correctly. I think that this was fixed in 8.0.0.4, but then popped up again in 8.0.0.10.
– Doug Grove
Mar 29 at 13:18
Wow. How about this error: wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.' That seems to be the genesis of the problem.
– Chibuike Arnold
Mar 30 at 17:45
Thanks for the reply Doug. Although, its difficult to ignore because my JBOSS keeps on looping with the same error, and my log file fills up to more than 1 Gigabyte due to the incessant looping. Also, Any message I manually put into one of my queues, gets moved to my Back-Out queue immediately jboss loads and connects with MQ. My Banking software also doesn't successfully send any message to MQ while JBOSS has connected. It's all strange to me because I just started using MQ and thought that after successfully connecting it to JBOSS and my application through those MDB setups, It'd work.
– Chibuike Arnold
Mar 25 at 18:12
Thanks for the reply Doug. Although, its difficult to ignore because my JBOSS keeps on looping with the same error, and my log file fills up to more than 1 Gigabyte due to the incessant looping. Also, Any message I manually put into one of my queues, gets moved to my Back-Out queue immediately jboss loads and connects with MQ. My Banking software also doesn't successfully send any message to MQ while JBOSS has connected. It's all strange to me because I just started using MQ and thought that after successfully connecting it to JBOSS and my application through those MDB setups, It'd work.
– Chibuike Arnold
Mar 25 at 18:12
Looking at the stack trace, you can see the 'afterDelivery()'. This means that the MDBs 'onMessage()' has returned. The transaction is then being rolled back. This means that the transaction was either marked in the code as being rollback only, or some exception occurred that caused the transaction to be rolled back.
– Doug Grove
Mar 27 at 12:40
Looking at the stack trace, you can see the 'afterDelivery()'. This means that the MDBs 'onMessage()' has returned. The transaction is then being rolled back. This means that the transaction was either marked in the code as being rollback only, or some exception occurred that caused the transaction to be rolled back.
– Doug Grove
Mar 27 at 12:40
Thanks for the reply Doug. I really appreciate it. A few more questions please. Any idea what could be causing the Transaction to rollback? I've been searching online, but I've not really been able to find out what causes the errors:1(xa_end has failed with error code '100') 2.(ARJUNA016045: attempted rollback of <*****failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4') 3.(IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener*****)
– Chibuike Arnold
Mar 28 at 12:38
Thanks for the reply Doug. I really appreciate it. A few more questions please. Any idea what could be causing the Transaction to rollback? I've been searching online, but I've not really been able to find out what causes the errors:1(xa_end has failed with error code '100') 2.(ARJUNA016045: attempted rollback of <*****failed with exception code XAException.XAER_NOTA: javax.transaction.xa.XAException: The method 'xa_rollback' has failed with errorCode '-4') 3.(IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener*****)
– Chibuike Arnold
Mar 28 at 12:38
The "Destroying connection that could not be successfully matched" is actually due to a bug in the IBM JCA client code. The transaction match check on the JMS session wasn't working correctly. I think that this was fixed in 8.0.0.4, but then popped up again in 8.0.0.10.
– Doug Grove
Mar 29 at 13:18
The "Destroying connection that could not be successfully matched" is actually due to a bug in the IBM JCA client code. The transaction match check on the JMS session wasn't working correctly. I think that this was fixed in 8.0.0.4, but then popped up again in 8.0.0.10.
– Doug Grove
Mar 29 at 13:18
Wow. How about this error: wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.' That seems to be the genesis of the problem.
– Chibuike Arnold
Mar 30 at 17:45
Wow. How about this error: wmq.jmsra.rar: MQJCA4026:Transaction backed out with reason: 'The method 'xa_end' has failed with errorCode '100'.' That seems to be the genesis of the problem.
– Chibuike Arnold
Mar 30 at 17:45
|
show 1 more comment
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55338902%2fim-having-an-xa-end-error-while-trying-to-send-a-message-from-my-banking-applic%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
