Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Mon, 24 Sep 2012 21:48:08 +1100 (NCT)
From: "Chris Poulsen (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <1899435882.116163.1348483688061.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1962867109.18332.1331805100134.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (JCR-3258) JTA & BundleDbPersistenceManager in
 autocommit mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JCR-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461717#comment-13461717 ] 

Chris Poulsen commented on JCR-3258:
------------------------------------

I see a variant of the same issue when using jcr from an ejb. On jboss as 5.1, jackrabbit 2.4.3 (jca connector).
                
> 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