Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Tue, 22 Feb 2011 10:21:38 +0000 (UTC)
From: =?utf-8?Q?Claus_K=C3=B6ll_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <574133775.7894.1298370098552.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1306191818.6200.1298311180577.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Assigned: (JCR-2901) JCR-2523 break the transaction handling
 in container managed environment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JCR-2901?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus K=C3=B6ll reassigned JCR-2901:
-------------------------------

    Assignee: Claus K=C3=B6ll

> JCR-2523 break the transaction handling in container managed environment
> ------------------------------------------------------------------------
>
>                 Key: JCR-2901
>                 URL: https://issues.apache.org/jira/browse/JCR-2901
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jca
>    Affects Versions: 2.1.3, 2.2.4
>         Environment: Container managed transactions on jboss 4.2.3  with =
spring-jcr-modules
>            Reporter: Andreas Zschorn
>            Assignee: Claus K=C3=B6ll
>            Priority: Blocker
>              Labels: Transaction,, container, managed
>         Attachments: testproject.zip
>
>
> during the cleanup (returning to the pool) of an jca managed connection, =
 an new internal session is created in the object JCAManagedConnection in t=
he method cleanup, this is supposed to fix JCR-2523, The sideeffect is, tha=
t the XA-Resource (variable-xaResource) in JCAManagedConnection is not anym=
ore 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, varia=
bles tx and txLog are null), because only the xaResource is informed about =
the new transaction context. Result is that the complete transaction handli=
ng does not work anymore.
> I attached a sample project which shows this behaviour.

--=20
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira