jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Müller <thomas.muel...@day.com>
Subject Re: DB inconsistency with Jackrabbit 1.6
Date Fri, 13 Nov 2009 09:11:07 GMT

This sounds like a bug, could you create a JIRA issue? It would be
great if you could include a simple test case; but as a minimum we
would need:

* The error message and stack trace (including all root causes; see
also the log file if there are more exceptions)
* The configuration (repository.xml and all workspace.xml files).
* The versions of the Jackrabbit jar files you use (the list of all
jar file names).

See also: http://wiki.apache.org/jackrabbit/QuestionsAndAnswers#Reporting_Problems


On Fri, Nov 13, 2009 at 3:55 AM, aasoj j <aas.ojj@gmail.com> wrote:
> Hi all,
> We are facing an issue while trying to update a node (Jackrabbit 1.6).
> We use MySQL for persistence. We observe the following exception in
> the logs:
> ERROR ClusterNode 672 http- Unable to commit log entry.
> org.apache.jackrabbit.core.journal.JournalException: Unable to append
> revision 133728.
>        at org.apache.jackrabbit.core.journal.DatabaseJournal.append(DatabaseJournal.java:593)
>        at org.apache.jackrabbit.core.journal.AppendRecord.update(AppendRecord.java:266)
>        at org.apache.jackrabbit.core.cluster.ClusterNode$WorkspaceUpdateChannel.updateCommitted(ClusterNode.java:667)
>        at org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedItemStateManager.java:765)
>        at org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedItemStateManager.java:1115)
>        at org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:351)
>        at org.apache.jackrabbit.core.state.XAItemStateManager.update(XAItemStateManager.java:354)
>        at org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemStateManager.java:326)
>        at org.apache.jackrabbit.core.state.SessionItemStateManager.update(SessionItemStateManager.java:325)
>        at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1111)
>        at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:915)
> When I looked into the DB, I saw the value of the current revision in
> GLOBAL_REVISIONS table was 133727. Strangely the JOURNAL table already
> had an entry with revision id 133728. This seems to be causing the
> exception.
> In the logs I saw the following error once:
> WARN DatabaseJournal 675 http- Error while committing
> connection: Can't call commit when autocommit=true
> Other than this I dont see anything unusual.
> Thanks in advance.
> Regards
> aasoj

View raw message