Joshua Braegger wrote:
Alan,
Sure thing, I've attached the two logs as well as the producer/consumer
test scripts I've been using.
brokerA.log is the broker I've been producing and consuming messages on,
and brokerB.log is the broker that I killed and attemped to have rejoin
the cluster.
Just to re-iterate, these are the steps I used to reproduce:
1. Start brokerA
2. Start brokerB
3. Start the consumer (run consumer.py). This uses brokerA
4. Produce 1 message (run producer.py). This uses brokerA
5. Kill brokerB
6. Start brokerB again
7. Produce 1 more message (run producer.py). This uses brokerA again.
8. Observe brokerB is down
Thanks for catching this. The python client starts numbering channels from 0,
which used to be illegal. The cluster didn't handle channel 0 properly. I fixed
it at both ends (C++ can handle channel 0 and python doesn't use it) in revision
771452.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
