jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Hendriks (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-1657) Cluster revision entries should be retrieved in order
Date Thu, 19 Jun 2008 09:45:44 GMT
Cluster revision entries should be retrieved in order
-----------------------------------------------------

                 Key: JCR-1657
                 URL: https://issues.apache.org/jira/browse/JCR-1657
             Project: Jackrabbit
          Issue Type: Bug
          Components: jackrabbit-core
    Affects Versions: 1.3.3
         Environment: Clustered
            Reporter: Martijn Hendriks
            Assignee: Martijn Hendriks


The selectRevisionStmtSQL (DatabaseJournal#buildSqlStatements) returns a result set which
may not be ordered by REVISION_ID. This has the effect that cluster instances that want to
synchronize to the latest revision do not update their local revision appropriately since
they assume that the revision result set is ordered (see code in AbstractJournal#doSync).
This might cause a lot of unnecessary CPU cycles on these machines with degraded performance
as a result. Furthermore, it causes functional issues as well as events may be fired multiple
times and in the wrong order.

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


Mime
View raw message