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/28 08:29:40 UTC

[jira] Commented: (JCR-1349) JNDIDatabasePersistenceManager calls commit

    [ 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.