[
https://issues.apache.org/jira/browse/JCR-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491266#comment-13491266
]
Jukka Zitting commented on JCR-3258:
------------------------------------
We need autocommit since Jackrabbit is using long-lived database connections.
Without autocommit we'd have to add an explicit COMMIT statement even after
each SELECT query as otherwise databases with high transaction isolation levels
would have to keep a transaction open potentially indefinitely.
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
