[
https://jira.jboss.org/jira/browse/JBMESSAGING-1734?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1734.
-----------------------------------
Resolution: Done
a 'retain.oldxabehaviour' property is defined to control the behavior.
2.3.2. retain.oldxabehaviour
This system property controls what kind of exception a JMS XAResource throws when the
prepare is called after
the connection is broken. If this property is not defined, an XAException with
XA_RBCOMMFAIL error code will
be thrown. If this propertie is defined, an XAException with XA_RETRY error code will be
thrown instead. JBM
by default doesn't define this property.
XAResource prepare() throwing XA_RETRY exception not compliant with
spec
-------------------------------------------------------------------------
Key: JBMESSAGING-1734
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1734
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Facade
Affects Versions: 1.4.0.SP3.CP08, 1.4.4.GA
Reporter: Howard Gao
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP09, 1.4.5.GA
On prepare phase, JBM throws XA_RETRY exception if the prepare request failed to be sent
through the connection. Due to the update in error handling of JBoss TX manager
(
https://jira.jboss.org/jira/browse/JBPAPP-564), it will cause problem if current JBM
works with the new TX manager. To be able to work properly with new TX manager, we need to
throw XA_RBCOMMFAIL instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira