Ok, I found the mistake with the session auto-commit problem ... I guess ... :-)
I had two datasources accessing the datastore. One is configured in the repository and I configured 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 and deleting the additional datasource there are no more strange "set auto-commit .." exceptions. Thx so far, Gamba Gamba wrote: > > version 1.6.0. reproducing it not easy, bit sometimes with multiple > threads the exception occurs. > > > > Alexander Klimetschek wrote: >> >> On Fri, Sep 11, 2009 at 10:01, Gamba <[email protected]> wrote: >>> 09:52:22,984 WARN [DbDataStore] Can not insert new record >>> java.sql.SQLException: You cannot set autocommit during a managed >>> transaction! >>> at >>> org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.setJdbcAutoCommit(BaseWrapperManagedConnection.java:582) >>> at >>> org.jboss.resource.adapter.jdbc.WrappedConnection.setAutoCommit(WrappedConnection.java:458) >>> at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryManager.setupConnection(ConnectionRecoveryManager.java:341) >>> at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryManager.reestablishConnection(ConnectionRecoveryManager.java:409) >>> at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryManager.getConnection(ConnectionRecoveryManager.java:159) >>> at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryManager.executeStmtInternal(ConnectionRecoveryManager.java:293) >>> at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryManager.executeStmt(ConnectionRecoveryManager.java:261) >>> at >>> org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryManager.executeStmt(ConnectionRecoveryManager.java:239) >>> at >>> org.apache.jackrabbit.core.data.db.DbDataStore.addRecord(DbDataStore.java:314) >>> at >>> org.apache.jackrabbit.core.value.BLOBInDataStore.getInstance(BLOBInDataStore.java:128) >>> at >>> org.apache.jackrabbit.core.value.InternalValue.getBLOBFileValue(InternalValue.java:658) >>> at >>> org.apache.jackrabbit.core.value.InternalValue.create(InternalValue.java:141) >>> at >>> org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:617) >>> at >>> org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:533) >>> at >>> org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2522) >>> at >>> de.handelshof.por.ejb.service.jcr.HMGJCRUserServiceBean.importFile(HMGJCRUserServiceBean.java:569) >>> ... >> >> 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. >> >> Regards, >> Alex >> >> -- >> Alexander Klimetschek >> [email protected] >> >> > > -- View this message in context: http://www.nabble.com/Confirming-assumptions-about-transactional-environment-and-session-handling-tp25378625p25449484.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
