transaction manager is not properly closing connections on slave server when slave server has exceptions. --------------------------------------------------------------------------------------------------------- Key: JBTM-189 URL: http://jira.jboss.com/jira/browse/JBTM-189 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Environment: JBossAS4.0.5, JBossTS4.2.2, multiple servers, distributed transactions. Reporter: Quande Ren Assigned To: Mark Little Priority: Critical This is fully discussed at the forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=97856 I am using JBoss4.0.5.GA and JBossTS4.2.2. I have a ServerA and ServerB and a client. here is my flow senario: Code: 1. client call a stateless session BeanA on ServerA, 2. BeanA do some pre work, 3. BeanA then call another stateless session BeanB on serverB, 4. BeanB do some work, 5. BeanA do some post work. the result shows that if either step 2 or step 5 failed, then the whole transaction get rollbacked correctly. but if step 4 failed, then transaction on ServerA rollback, but the transaction on ServerB does not get rollbacked or committed, we can see the debug information says the xa datasource transaction get started but never get rollbacked. and the database connection remains in use, and when we run the test several times, all the database connections will used up. -- 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