[
https://issues.apache.org/jira/browse/JCR-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413502#comment-13413502
]
Claus Köll commented on JCR-3378:
---------------------------------
The problem comes from pooling the prepared statements. In XA Environment the
connection is shared in batchMode based on the global transactionId. If more xa
clients read and write to the same node
the prepared statement will be closed while a other one is reading from a
resultset from the same statement. I tried to disable prepapared statement
pooling and it works fine now.
> The ConnectionHelper can return a closed Connection in BatchMode
> ----------------------------------------------------------------
>
> Key: JCR-3378
> URL: https://issues.apache.org/jira/browse/JCR-3378
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.4.2
> Reporter: Claus Köll
> Assignee: Claus Köll
>
> It is possible that the method inBatchMode() returns true and meanwhile the
> connection will be closed.
> Closing the Connection and removing it from BatchMode is not synchronized. I
> must check if we can handle it by order the close and remove.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
