[ http://jira.jboss.com/jira/browse/JBAS-3183?page=comments#action_12340105 ] Dimitris Andreadis commented on JBAS-3183: ------------------------------------------ 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. -- 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