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/04/27 10:53:15 UTC

[jira] Resolved: (JCR-884) DatabaseJournal assigns same revision id to different revisions

     [ https://issues.apache.org/jira/browse/JCR-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominique Pfister resolved JCR-884.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3

Fixed by saving away the locked revision number in the record being appended.

Fixed in revision 533019.

> DatabaseJournal assigns same revision id to different revisions
> ---------------------------------------------------------------
>
>                 Key: JCR-884
>                 URL: https://issues.apache.org/jira/browse/JCR-884
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.3
>            Reporter: Dominique Pfister
>         Assigned To: Dominique Pfister
>             Fix For: 1.3
>
>
> Running a transaction that updates multiple workspaces (e.g. a versioning operation) will fail in DatabaseJournal, because every individual update will ultimately be assigned the same revision id. An indication of this failure when e.g. using Oracle as backend for journaling will look as follows::
> java.sql.SQLException: ORA-00001: unique constraint (JOURNAL_IDX) violated
>  at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
>  at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
>  at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:590)
>  at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1973)
>  at oracle.jdbc.ttc7.TTC7Protocol.executeFetch(TTC7Protocol.java:977)
>  at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2205)
>  at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:2064)
>  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2989)
>  at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:658)
>  at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:736)
>  at org.apache.jackrabbit.core.journal.DatabaseJournal.append(DatabaseJournal.java:293)
>  ... 24 more
> This bug has been reported by Rafał Kwiecień.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.