Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <2428321.1196784823225.JavaMail.jira@brutus>
Date: Tue, 4 Dec 2007 08:13:43 -0800 (PST)
From: "Dominique Pfister (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-1254) DatabaseJournal commits twice inside a
 transaction, causing an error with MySQL
In-Reply-To: <2083189.1196782243088.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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