jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCR-3258) JTA & BundleDbPersistenceManager in autocommit mode
Date Mon, 05 Nov 2012 14:10:53 GMT

     [ https://issues.apache.org/jira/browse/JCR-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting resolved JCR-3258.

    Resolution: Not A Problem

Jackrabbit is designed to work directly as an XA resource, which means that the underlying
database should *not* be controlled by a transaction manager. Instead, to properly implement
transaction semantics, Jackrabbit needs to be in control of the underlying database connection.
> 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

View raw message