[jboss-jira] [JBoss JIRA] Resolved: (JBAS-3183) Integration with WebSphere MQ 5.x
[ http://jira.jboss.com/jira/browse/JBAS-3183?page=all ]
Weston Price resolved JBAS-3183.
--------------------------------
Resolution: Done
A new JcaXAResourceWrapper has been added to allow for the isSameRMOverrideValue
mechanism. This will enable JBoss to enlist multiple WASMQ resources in the same
transaction. Note, the configuration for this will be specified on the Wiki, but the short
of it is that the isSameRMOverrideValue is now configurable per
datasource/connection-factory definition; it is not just for JDBC resources. Depending
upon demmand, this fix may need to be ported to previous JBoss releases to address WASMQ
integration issues.
Integration with WebSphere MQ 5.x
---------------------------------
Key: JBAS-3183
URL: http://jira.jboss.com/jira/browse/JBAS-3183
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS service
Environment: WebSphereMQ 5.3 with Extended TX client
Reporter: Luc Texier
Assigned To: Weston Price
Priority: Critical
Fix For: JBossAS-4.2.0.CR1
Attachments: mq-trace.jar, mq-xa.zip
http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA...
we need to make some changes to StdServerSession and StdServerSessionPool to integrate
two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource
implementation and transaction handling
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira