From users-return-12614-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Tue Sep 15 07:44:40 2009 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 69109 invoked from network); 15 Sep 2009 07:44:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Sep 2009 07:44:40 -0000 Received: (qmail 77906 invoked by uid 500); 15 Sep 2009 07:44:39 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 77880 invoked by uid 500); 15 Sep 2009 07:44:39 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 77869 invoked by uid 99); 15 Sep 2009 07:44:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 07:44:39 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 07:44:28 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MnShr-0007BZ-F2 for users@jackrabbit.apache.org; Tue, 15 Sep 2009 00:44:07 -0700 Message-ID: <25449484.post@talk.nabble.com> Date: Tue, 15 Sep 2009 00:44:07 -0700 (PDT) From: Gamba To: users@jackrabbit.apache.org Subject: Re: Confirming assumptions about transactional environment and session-handling In-Reply-To: <25397371.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: holger.breuer@handelshof.de References: <25378625.post@talk.nabble.com> <25382645.post@talk.nabble.com> <25396705.post@talk.nabble.com> <25397371.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Ok, I found the mistake with the session auto-commit problem ... I guess ..= .=20 :-) I had two datasources accessing the datastore. One is configured in the repository and I configured=20 an other, which was referenced from repository.xml (to reference the user name by jndi I think). It was a piece of testcode from my early days with jackrabbit. After referencing the datastore directly from repository.xml an= d deleting the additional datasource there are no more strange "set auto-commit .." exceptions.=20 Thx so far, Gamba Gamba wrote: >=20 > version 1.6.0. reproducing it not easy, bit sometimes with multiple > threads the exception occurs. >=20 >=20 >=20 > Alexander Klimetschek wrote: >>=20 >> On Fri, Sep 11, 2009 at 10:01, Gamba wrote= : >>> 09:52:22,984 WARN =C2=A0[DbDataStore] Can not insert new record >>> java.sql.SQLException: You cannot set autocommit during a managed >>> transaction! >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.setJdbcAut= oCommit(BaseWrapperManagedConnection.java:582) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.jboss.resource.adapter.jdbc.WrappedConnection.setAutoCommit(Wrapped= Connection.java:458) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMa= nager.setupConnection(ConnectionRecoveryManager.java:341) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMa= nager.reestablishConnection(ConnectionRecoveryManager.java:409) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMa= nager.getConnection(ConnectionRecoveryManager.java:159) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMa= nager.executeStmtInternal(ConnectionRecoveryManager.java:293) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMa= nager.executeStmt(ConnectionRecoveryManager.java:261) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryMa= nager.executeStmt(ConnectionRecoveryManager.java:239) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.data.db.DbDataStore.addRecord(DbDataStore.ja= va:314) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.value.BLOBInDataStore.getInstance(BLOBInData= Store.java:128) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.value.InternalValue.getBLOBFileValue(Interna= lValue.java:658) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.value.InternalValue.create(InternalValue.jav= a:141) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:617) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:533) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2522) >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at >>> de.handelshof.por.ejb.service.jcr.HMGJCRUserServiceBean.importFile(HMGJ= CRUserServiceBean.java:569) >>> ... >>=20 >> Sounds like https://issues.apache.org/jira/browse/JCR-1013 but for the >> DbDataStore. What version of Jackrabbit are you using? JCR-1013 should >> be fixed since 1.4. >>=20 >> Regards, >> Alex >>=20 >> --=20 >> Alexander Klimetschek >> alexander.klimetschek@day.com >>=20 >>=20 >=20 >=20 --=20 View this message in context: http://www.nabble.com/Confirming-assumptions-= about-transactional-environment-and-session-handling-tp25378625p25449484.ht= ml Sent from the Jackrabbit - Users mailing list archive at Nabble.com.