qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] Created: (QPID-3121) Cluster management inconsistency when using persistent store.
Date Mon, 07 Mar 2011 15:51:59 GMT
Cluster management inconsistency when using persistent store.

                 Key: QPID-3121
                 URL: https://issues.apache.org/jira/browse/QPID-3121
             Project: Qpid
          Issue Type: Bug
          Components: C++ Clustering
    Affects Versions: 0.9
            Reporter: Alan Conway
            Assignee: Alan Conway
             Fix For: 0.9

If cluster_tests.py, test_management is modified to enable durable messages. The log comparison
at end of test sometimes shows messages like this on one broker but not the others:

trace Changed V1 statistics org.apache.qpid.broker:connection:
trace Changed V2 statistics org.apache.qpid.broker:connection:

To date this hasn't been seen to actually cause a cluster crash but in principle it is possible
it could.

To reproduce, build the message store at: http://anonsvn.jboss.org/repos/rhmessaging/store/
In the tests/cluster directory, run this in a loop:

make check TESTS=run_python_cluster_tests CLUSTER_TESTS='*.test_management* -DDURATION=2'

It will fail, usually on the first iteration, showing the log files that don't match. Use
diff or other such tool to confirm that the mismatched lines are as above. The file may also
contain some other mismatches showing a different number of stats in a periodic update - that
is a consequence of the above.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message