[
https://issues.apache.org/jira/browse/JCR-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605185#comment-13605185
]
Roland Stamm commented on JCR-3276:
-----------------------------------
I am having the same problem with Weblogic 10.3.3 when using a nested
transaction. (works fine on Jboss 5.1)
Scenario:
tx #1 begin()
do user session work
tx #1 suspend()
tx #2 begin()
do admin session work
tx #2 commit()
tx #1 resume()
do user session work
tx #1 commit()
When tx #1 should resume I am getting following exception:
{code}
Caused by: java.lang.IllegalStateException: Inactive logical session handle
called
at
org.apache.jackrabbit.jca.JCAManagedConnection.getSession(JCAManagedConnection.java:350)
at
org.apache.jackrabbit.jca.JCASessionHandle.getSession(JCASessionHandle.java:90)
at
org.apache.jackrabbit.jca.JCASessionHandle.getWorkspace(JCASessionHandle.java:125)
{code}
When using the supplied patch resuming tx #1 works.
> JCA Adpater not handling transaction suspension correctly
> ---------------------------------------------------------
>
> Key: JCR-3276
> URL: https://issues.apache.org/jira/browse/JCR-3276
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jca
> Affects Versions: 2.2.11, 2.4
> Environment: Weblogic 10.3.5
> Reporter: Daniel Hasler
> Attachments: JCR-3276.diff
>
>
> The JCA Adapter does not distinguish the case where a Container just wants to
> suspend the current transaction and closes the connection handle in any case.
> The attached patch just checks if the container wants to suspend the current
> transaction and does not close the connection handle in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
