You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <qp...@incubator.apache.org> on 2009/12/09 16:55:18 UTC
[jira] Created: (QPID-2253) Cluster node shutsdown with
inconsistent error
Cluster node shutsdown with inconsistent error
-----------------------------------------------
Key: QPID-2253
URL: https://issues.apache.org/jira/browse/QPID-2253
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.5
Reporter: Alan Conway
Assignee: Alan Conway
Fix For: 0.6
Description of problem:
When running the "test_failover" test case in the qpid-python-testkit framework
where cluster nodes are shutdown and new members are added, a new node just
joined encounters an error of the form "confirmed N but only sent N-1" which is
only raised on the said member causing it to shut down as inconsistent.
Version-Release number of selected component (if applicable):
qpid trunk
How reproducible:
Always
Steps to Reproduce:
1. checkout svn
2. build c++ broker and cluster module
3. go to java/testkit/bin and run ./qpid-python-testkit
Actual results:
cluster2-5: 2009-12-04 14:44:35 notice cluster(192.168.1.103:14491 READY)
caught up, active cluster member.
cluster2-5: 2009-12-04 14:44:36 error Execution exception: invalid-argument:
anonymous.e3a66a8d-330d-47c2-b96d-bb0b1315248b: confirmed < (2+0) but only sent
< (1+0) (qpid/SessionState.cpp:151)
cluster2-5: 2009-12-04 14:44:36 critical cluster(192.168.1.103:14491
READY/error) local error 599 did not occur on member 192.168.1.103:14453:
invalid-argument: anonymous.e3a66a8d-330d-47c2-b96d-bb0b1315248b: confirmed <
(2+0) but only sent < (1+0) (qpid/SessionState.cpp:151)
cluster2-5: 2009-12-04 14:44:36 error Error delivering frames: local error did
not occur on all cluster members : invalid-argument:
anonymous.e3a66a8d-330d-47c2-b96d-bb0b1315248b: confirmed < (2+0) but only sent
< (1+0) (qpid/SessionState.cpp:151) (qpid/cluster/ErrorCheck.cpp:89)
cluster2-5: 2009-12-04 14:44:36 notice cluster(192.168.1.103:14491 LEFT/error)
leaving cluster cluster2-helaya:13958
cluster2-5: 2009-12-04 14:44:36 notice Shut down
Expected results:
There should not be any inconsistent errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-2253) Cluster node shutsdown with
inconsistent error
Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway resolved QPID-2253.
-------------------------------
Resolution: Fixed
Fixed in r888874
> Cluster node shutsdown with inconsistent error
> -----------------------------------------------
>
> Key: QPID-2253
> URL: https://issues.apache.org/jira/browse/QPID-2253
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.5
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.6
>
>
> Description of problem:
> When running the "test_failover" test case in the qpid-python-testkit framework
> where cluster nodes are shutdown and new members are added, a new node just
> joined encounters an error of the form "confirmed N but only sent N-1" which is
> only raised on the said member causing it to shut down as inconsistent.
> Version-Release number of selected component (if applicable):
> qpid trunk
> How reproducible:
> Always
> Steps to Reproduce:
> 1. checkout svn
> 2. build c++ broker and cluster module
> 3. go to java/testkit/bin and run ./qpid-python-testkit
> Actual results:
> cluster2-5: 2009-12-04 14:44:35 notice cluster(192.168.1.103:14491 READY)
> caught up, active cluster member.
> cluster2-5: 2009-12-04 14:44:36 error Execution exception: invalid-argument:
> anonymous.e3a66a8d-330d-47c2-b96d-bb0b1315248b: confirmed < (2+0) but only sent
> < (1+0) (qpid/SessionState.cpp:151)
> cluster2-5: 2009-12-04 14:44:36 critical cluster(192.168.1.103:14491
> READY/error) local error 599 did not occur on member 192.168.1.103:14453:
> invalid-argument: anonymous.e3a66a8d-330d-47c2-b96d-bb0b1315248b: confirmed <
> (2+0) but only sent < (1+0) (qpid/SessionState.cpp:151)
> cluster2-5: 2009-12-04 14:44:36 error Error delivering frames: local error did
> not occur on all cluster members : invalid-argument:
> anonymous.e3a66a8d-330d-47c2-b96d-bb0b1315248b: confirmed < (2+0) but only sent
> < (1+0) (qpid/SessionState.cpp:151) (qpid/cluster/ErrorCheck.cpp:89)
> cluster2-5: 2009-12-04 14:44:36 notice cluster(192.168.1.103:14491 LEFT/error)
> leaving cluster cluster2-helaya:13958
> cluster2-5: 2009-12-04 14:44:36 notice Shut down
> Expected results:
> There should not be any inconsistent errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org