Bug 696637 - exchanges with IVE option cause cluster inconsistencies in updatees
Summary: exchanges with IVE option cause cluster inconsistencies in updatees
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 2.0
: ---
Assignee: Alan Conway
QA Contact: Petr Matousek
URL:
Whiteboard:
Depends On:
Blocks: 723471 703887 716252
TreeView+ depends on / blocked
 
Reported: 2011-04-14 13:46 UTC by Gordon Sim
Modified: 2011-07-20 10:01 UTC (History)
5 users (show)

Fixed In Version: qpid-cpp-mrg-0.10-4
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 703887 716252 (view as bug list)
Environment:
Last Closed: 2011-06-23 15:43:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0890 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 2.0 Release 2011-06-23 15:42:41 UTC

Description Gordon Sim 2011-04-14 13:46:40 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. start a cluster node

2. create an exchange with the IVE option 
  qpid-config add exchange topic my-topic-exchange --ive

3. send a message to that exchange
 
  spout --content abc my-topic-exchange/my-key

4. start another node in the cluster
5. create a queue and bind it to the exchange created in 2. using the key with which the message was sent in 3.

  qpid-config add queue my-queue
  qpid-config bind my-topic-exchange my-queue my-key

(queue is now inconsistent; on the first node it has a message, on the second it has none)

6. run ./src/tests/qpid-receive --capacity 1 --address 'my-queue; {mode: browse}' against the first node
  
Actual results:

second node shutsdown with something like:

2011-04-14 14:33:04 error Execution exception: invalid-argument: anonymous.35276a61-4f3a-46a9-a070-e88c6c6ac01f: confirmed < (2+0) but only sent < (1+0) (../../src/qpid/SessionState.cpp:154)
2011-04-14 14:33:04 critical cluster(192.168.0.3:9532 READY/error) local error 832 did not occur on member 192.168.0.3:9482: invalid-argument: anonymous.35276a61-4f3a-46a9-a070-e88c6c6ac01f: confirmed < (2+0) but only sent < (1+0) (../../src/qpid/SessionState.cpp:154)


Expected results:

no shutdown and the command in 6 can be repeated against wither node with the same results

Additional info:

Root of the problem is that exchange with IVE holds extra state in the form of the 'last message', and this is not transferred to new members.

Comment 1 Alan Conway 2011-04-19 18:56:29 UTC
Upstream https://issues.apache.org/jira/browse/QPID-3217

Comment 2 Ted Ross 2011-04-19 21:09:15 UTC
Fixed upstream (by aconway) in revision 1095209

Comment 4 Petr Matousek 2011-05-11 14:37:21 UTC
This issue has been fixed in qpid-cpp-mrg-0.10-4 for RHEL5, but not yet
available in any RHEL6 package. 

The bug was cloned for RHEL6: please see bug 703887

Verified on RHEL5.6 architectures: i386, x86_64

packages installed:
python-qpid-0.10-1.el5
python-qpid-qmf-0.10-6.el5
qpid-cpp-client-0.10-4.el5
qpid-cpp-client-devel-0.10-4.el5
qpid-cpp-client-devel-docs-0.10-4.el5
qpid-cpp-client-ssl-0.10-4.el5
qpid-cpp-mrg-debuginfo-0.10-4.el5
qpid-cpp-server-0.10-4.el5
qpid-cpp-server-cluster-0.10-4.el5
qpid-cpp-server-devel-0.10-4.el5
qpid-cpp-server-ssl-0.10-4.el5
qpid-cpp-server-store-0.10-4.el5
qpid-cpp-server-xml-0.10-4.el5
qpid-java-client-0.10-4.el5
qpid-java-common-0.10-4.el5
qpid-java-example-0.10-4.el5
qpid-qmf-0.10-6.el5
qpid-qmf-devel-0.10-6.el5
qpid-tools-0.10-4.el5

-> VERIFIED

Comment 5 errata-xmlrpc 2011-06-23 15:43:06 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0890.html


Note You need to log in before you can comment on or make changes to this bug.