You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jarle B. Hjortland (JIRA)" <ji...@apache.org> on 2008/01/25 14:23:34 UTC
[jira] Created: (JCR-1349) JNDIDatabasePersistenceManager calls
commit
JNDIDatabasePersistenceManager calls commit
-------------------------------------------
Key: JCR-1349
URL: https://issues.apache.org/jira/browse/JCR-1349
Project: Jackrabbit
Issue Type: Bug
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.
[jira] Updated: (JCR-1349) JNDIDatabasePersistenceManager calls
commit
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller updated JCR-1349:
--------------------------------
Issue Type: New Feature (was: Bug)
Jackrabbit does not support this mode of operation right now.
To support it, we would need to define exactly how this mode should behave,
for example: should the Session.save() calls be silently ignored, or should they
throw an exception (like commit() throws an exception).
> 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.
[jira] Commented: (JCR-1349) JNDIDatabasePersistenceManager calls
commit
Posted by "Michael Braunschweig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848845#action_12848845 ]
Michael Braunschweig commented on JCR-1349:
-------------------------------------------
The solution for WebSphere application server is:
Navigate to Resources - JDBC - Data sources - <data source> - Custom properties
add property nonTransactionalDataSource with value true
> JNDIDatabasePersistenceManager calls commit
> -------------------------------------------
>
> Key: JCR-1349
> URL: https://issues.apache.org/jira/browse/JCR-1349
> Project: Jackrabbit Content Repository
> 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.
[jira] Commented: (JCR-1349) JNDIDatabasePersistenceManager calls
commit
Posted by "Jarle B. Hjortland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563064#action_12563064 ]
Jarle B. Hjortland commented on JCR-1349:
-----------------------------------------
If Session.save() does not else than commit the connections, it could fail or log an warning ("Session.save on a managed connection will not commit to the DB").
So for now the only solution to my problem is to create an EJB with transactions disabled. (Manually defined connections is not a option).
> 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.
[jira] Commented: (JCR-1349) JNDIDatabasePersistenceManager calls
commit
Posted by "Marcel May (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565163#action_12565163 ]
Marcel May commented on JCR-1349:
----------------------------------
Deploy Jackrabbit using the JCA adapter and configure an unmanaged datasource (For JBoss: <no-tx-datasource/>).
> 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.
[jira] Commented: (JCR-1349) JNDIDatabasePersistenceManager calls
commit
Posted by "Dirk Feufel (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (JCR-1349) JNDIDatabasePersistenceManager calls
commit
Posted by "Dirk Feufel (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848848#action_12848848 ]
Dirk Feufel commented on JCR-1349:
----------------------------------
I will be out of the office till April 11th 2010. I will respond to your e-mail as soon as possible on my return. Please note, that your mail will not be forwarded. In urgent cases please contact support@de.cordys.com.
> JNDIDatabasePersistenceManager calls commit
> -------------------------------------------
>
> Key: JCR-1349
> URL: https://issues.apache.org/jira/browse/JCR-1349
> Project: Jackrabbit Content Repository
> 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.