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 I'm at r769550 -Josh On Fri, May 1, 2009 at 6:39 AM, Alan Conway <[email protected]> wrote: > > Try running with --trace argument to brokers and send the logs from brokers > A & B (they'll be quite big) > > If you have a simple test client that demonstrates the problem attach that > too. > > What SVN revision or what release of Qpid are you using? > > I'll look into this... > > Cheers, > Alan. >
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
