You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dominique Pfister (JIRA)" <ji...@apache.org> on 2007/12/04 17:13:43 UTC
[jira] Resolved: (JCR-1254) DatabaseJournal commits twice inside a
transaction, causing an error with MySQL
[ https://issues.apache.org/jira/browse/JCR-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominique Pfister resolved JCR-1254.
------------------------------------
Resolution: Fixed
Assignee: Dominique Pfister
Fixed by introducing a lock-level that will reset auto-commit to true only when the final unlock() on the journal has been called, in revision 600980. Thanks to Dainius Rygelis for reporting.
> DatabaseJournal commits twice inside a transaction, causing an error with MySQL
> -------------------------------------------------------------------------------
>
> Key: JCR-1254
> URL: https://issues.apache.org/jira/browse/JCR-1254
> Project: Jackrabbit
> Issue Type: Bug
> Components: clustering
> Affects Versions: 1.3.3
> Reporter: Dominique Pfister
> Assignee: Dominique Pfister
>
> When committing a transaction in a clustered setup, multiple records may be appended to the DatabaseJournal. After having appended a record, commit() is called on the connection and auto-commit mode is again enabled. Apart from not being semantically correct, committing a connection that is already in auto-commit mode throws an error when using MySQL as backend.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.