[jboss-jira] [JBoss JIRA] Commented: (JBAS-3183) Integration with WebSphere MQ 5.x

Wed Jul 26 11:26:11 EDT 2006

    [ http://jira.jboss.com/jira/browse/JBAS-3183?page=comments#action_12340105 ] 

Dimitris Andreadis commented on JBAS-3183:
------------------------------------------

>From Adrian:

This has two parts:
1) Testing and backporting the server session pool changes from head
2) Finding a workaround for the TM_JOIN hang bug within WSMQ.

The problem is exhibited by the following pseudo code:

Transaction tx = transactionManager.begin();

Connection c1 = wsmqConnectionFactory.createXAConnection();
XAResource xar1 = getXAResource(c1); tx.start(xar1, TM_NOFLAGS);

Connection c2 = wsmqConnectionFactory.createXAConnection();
XAResource xar2 = getXAResource(c2); tx.start(xar2, TM_JOIN); // IT 
HANGS HERE IN WSMQ CODE!!!!

So the problem is in WSMQ. Any "fix" would be a workaround to an IBM bug.

> 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: Adrian Brock
>            Priority: Critical
>             Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.1.CR1
>
>
> http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossASPart2
> 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