[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1786?page=c... ] Gary Sargent commented on HHH-1786: ----------------------------------- Having looked into this further, in JTASessionContext, the map is being populated with a different key to that used when it is being read (in the two places a get and a remove are performed on the Map). This will work fine for non-Websphere transaction lookups as the default implementation returns the transaction, which is what is used for the get / remove. For WebSphere, this won't work as this uses a different key. This means a new session is ALWAYS created even if one exists, and sessions are NEVER removed! Solution is to ensure the correct key is used in the get and remove methods on the Map. Diff for JTASessionContext.java against 3.3.0 is: 104c104,107 < Session currentSession = ( Session ) currentSessionMap.get( txn ); --- 110c113 < txn.registerSynchronization( buildCleanupSynch( txn ) ); --- 122,124d124 < Object txnIdentifier = factory.getSettings().getTransactionManagerLookup() == null < ? txn < : factory.getSettings().getTransactionManagerLookup().getTransactionIdentifier( txn ); 131,132c131,132 < private CleanupSynch buildCleanupSynch(Transaction txn) { < return new CleanupSynch( txn, this ); --- 183c183 < private Transaction txn; --- 186,187c186,187 < public CleanupSynch(Transaction txn, JTASessionContext context) { < this.txn = txn; --- 201c201 < context.currentSessionMap.remove( txn ); --- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira