Bug 500174

Description of problem:

If a new cluster member is added after broker objects (queues, exchanges etc) are added to the original cluster nodes, then the new member allocates different management ids to those objects.

This causes problems when e.g. a management method is invoked

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

qpidd-0.5.752581-5.el5

How reproducible:

100%

Steps to Reproduce:
1. start one cluster node 
2. add a queue (e.g. qpid-config add queue test-queue)
3. start new node for the same cluster
4. send 5 messages to the queue (e.g. for m in A B C D E; do echo $m; done | ./src/tests/sender --send-eos 1 -p NODE_1)
5. connect to one node with qpid-tool and invoke purge on the queue specifying 3 messages should be removed (e.g. call <ID> purge 3)
6. exit qpid-tool and consume messages from the other node (i.e. not the one we just connected to using qpid-tool) (e.g. ./src/tests/receiver -p NODE_2)
  
Actual results:

All 5 message are received although three were purged off the other node. The other node also crashes with something like: 

error Execution exception: invalid-argument: anonymous.04e9044c-211f-403e-863a-fbeb0704566b: confirmed < (4+0) but only sent < (3+0) (qpid/SessionState.cpp:151)

Expected results:

Purge should work consistently across cluster, leaving 2 messages on the queue in all nodes. Subsequent use of cluster should not cause crashes.

Additional info:

You can also just check using qpid-tool that the queues have different ids after step 3 above, which is the root of the problem.

(sender and receiver test programs used in examples above are from qpid svn)