[
https://issues.apache.org/jira/browse/JCR-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591961#action_12591961
]
Dirk Feufel commented on JCR-1349:
----------------------------------
Same problem with WebSphere and datasources. In addition Prepared Statements
should not be cached and reused.
Here some hints were to start:
Caused by: java.sql.SQLException: DSRA9350E: Operation Connection.commit is not
allowed during a global transaction.
at
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.commit(WSJdbcConnection.java:922)
at
org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.store(DatabasePersistenceManager.java:315)
com.ibm.websphere.ce.cm.ObjectClosedException: DSRA9110E: Statement is closed.
at
com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.runtimeXIfNotClosed(WSJdbcStatement.java:1505)
at
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.setObject(WSJdbcPreparedStatement.java:1408)
at
org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.executeStmt(DatabasePersistenceManager.java:855)
at
org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager.store(DatabasePersistenceManager.java:480)
> JNDIDatabasePersistenceManager calls commit
> -------------------------------------------
>
> Key: JCR-1349
> URL: https://issues.apache.org/jira/browse/JCR-1349
> Project: Jackrabbit
> Issue Type: New Feature
> Components: jackrabbit-core
> Affects Versions: 1.4
> Reporter: Jarle B. Hjortland
>
> It is not possible to configure either JNDIDatabasePersistenceManager or
> BundleDbPersistenceManager to use a Managed Datasource. Methods like
> setAutoCommit, commit and rollback should not be called on managed
> connections.
> Try to run Jackrabbit within JBOSS or Apache Geronimo and you should face the
> same problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
