[
https://issues.apache.org/jira/browse/JCR-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412420#comment-13412420
]
Carl Pritchett commented on JCR-3258:
-------------------------------------
We get the same issue - the BundleDBPersistenceManager uses the
ConnectionHelper via getConnection() and this always sets autoCommit to true.
I'm using a Spring transaction - and this causes a similar error to the error
in the description.
org.apache.jackrabbit.core.state.ItemStateException: failed to read bundle:
fa395a84-99e0-46c1-8d89-ff62c3f6c4d9: java.sql.SQLException: You cannot set
autocommit during a managed transaction!
When can use "NOT_SUPPORTED" but I'd prefer not to for obvious reasons.
Perhaps there is a way to use XASessions to do this and I'd love a link to the
doco on how, but can we turn off autoCommit via an option when not running in a
cluster?
> JTA & BundleDbPersistenceManager in autocommit mode
> ---------------------------------------------------
>
> Key: JCR-3258
> URL: https://issues.apache.org/jira/browse/JCR-3258
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.4
> Environment: Postgresql 8.4
> BTM 2.1.2
> Jencks 2.0
> Reporter: YP
> Priority: Blocker
> Attachments: jca.log, non-jca.log
>
>
> Neither JTA nor JCA with JTA works because of the exception
> 'java.sql.SQLException: autocommit is not allowed on a resource enlisted in a
> global transaction' from BTM,
> issue JCR-1253 has explanation of why keep autocommit enabled, but there is
> always error when autocommit mode is true.
--
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
