Bug 702108

Summary:	Qpid JCA Adapter doesn't work with clustered qpidd
Product:	Red Hat Enterprise MRG	Reporter:	Weston M. Price <wprice>
Component:	qpid-jca	Assignee:	Andrew Stitcher <astitcher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	Development	CC:	astitcher, cdewolf, iboverma, jpechane, jsedlace, tross
Target Milestone:	2.1.2
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-07 17:41:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	727182
Bug Blocks:

Description Weston M. Price 2011-05-04 19:18:37 UTC

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.

Comment 1 Andrew Stitcher 2011-05-13 04:53:39 UTC

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.

Comment 4 Weston M. Price 2011-09-10 12:26:50 UTC

Just keeping an eye out on

https://issues.apache.org/jira/browse/QPID-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel