[ https://issues.apache.org/jira/browse/AMQ-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-5311. ----------------------------- Resolution: Fixed fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/ab1e9c78 > XAException message should encode the xaErrorCode > ------------------------------------------------- > > Key: AMQ-5311 > URL: https://issues.apache.org/jira/browse/AMQ-5311 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, JMS client > Affects Versions: 5.10.0 > Reporter: Gary Tully > Assignee: Gary Tully > Labels: errorCode, xa > Fix For: 5.11.0 > > > openwire will only marshall the message string, so an XAException will always > be initialised clients side with errorCode=0, which maps to XA_OK or an > invalid error code. > Appending xaErrorCode:X to the message will allow the XAException.errorCode > to be extracted client side and propagated correctly, so a TM can respond to > an XAER_NOTA. > Currently we set a generic XAER_RMERR which can force the TM to retry. -- This message was sent by Atlassian JIRA (v6.2#6252)