[
http://jira.jboss.com/jira/browse/JBAS-3183?page=comments#action_12340413 ]
Weston Price commented on JBAS-3183:
------------------------------------
Well, if it's that critical, then I suggest we open a support account (unless we
already have one) with IBM. I am not sure what type of 'workaround' you expect to
be delivered for an IBM related defect especially in the time frame. Can someone tell me
why this can't be delivered to this client as a patch after the 4.0.5CR1 release and
why an issue with IBM's MQ code has to hold up our release?
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: Blocker
Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.1.CR1
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