Description of problem: As reported from the field, there is an issue with using the Qpid JCA adapter in a cluster configuration. This involves the outbound connection factory. Internally, the QpidRAManagedConnection only keeps a reference to an XASession/XAResource to managed connectivity. As a result, the Broker, when running in a cluster, interprets the session/connection to be under XA regardless of whether or not the two phase commit protocol is in use. Being that XA is not allowed in a cluster config, an exception is reported rendering outbound connectivity in this scenario unusable. Version-Release number of selected component (if applicable): Current development version of the Qpid JCA adapter. How reproducible: Consistent. Steps to Reproduce: 1.Deploy any JCA outbound connection factory connecting to a QPID broker running in a cluster 2. 3. Actual results: JMSException: DTX transaction are not currently supported by cluster Expected results: JMSException: DTX transaction are not currently supported by cluster Additional info: This was reported in the field and as such only involves outbound connectivity in a cluster. All other deployment, configuration scenarios are still supported.
The applied fix uses an new property on the Connection Factory to force the connection to use local transactions not DTX. It is kind of a work around as you can't get distributed transactions at all with the current clustered broker.
Just keeping an eye out on https://issues.apache.org/jira/browse/QPID-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel