[JCR-2901] JCR-2523 break the transaction handling in container managed environment

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.1.3, 2.2.4
• Fix Version/s: 2.1.5, 2.2.5
• Component/s: jackrabbit-jca
• Labels: Transaction, container managed
• Environment: Container managed transactions on jboss 4.2.3 with spring-jcr-modules
• Assignee: Claus Köll
• Reporter: Andreas Zschorn
• Created: 21/Feb/11 17:59
• Updated: 24/May/11 15:50
• Resolved: 24/Feb/11 13:39

Description

during the cleanup (returning to the pool) of an jca managed connection, an new internal session is created in the object JCAManagedConnection in the method cleanup, this is supposed to fix JCR-2523, The sideeffect is, that the XA-Resource (variable-xaResource) in JCAManagedConnection is not anymore the same XASessionImpl Object like the session Object. Subsequent calls on this connection, lead that the internal session variable is not anymore informed about the current transaction context. (XAItemStateManager, variables tx and txLog are null), because only the xaResource is informed about the new transaction context. Result is that the complete transaction handling does not work anymore.
I attached a sample project which shows this behaviour.