On 05/18/2011 06:57 AM, stoyan wrote:
hello
i seem to have had a network failure in my cluster of two nodes - main node
A lived on, while on node B qpid quit.
now, there are two queues (Q1, Q2 with same routing key) and after this
incident broker A kept receiving messages to these queues.
after some time i tried to restart node B and couldn't - first i tried with
its data-dir untouched, then i removed the data dir contents altogether.
judging by the qpid logs, the B broker joined the cluster and started
receiving state updates; it read all the messages for queue Q1 and then died
when reading the first message for Q2, the last log message is
'qpid.cluster-update: recv cmd 28: content (267 bytes)<?xml version="1.0"
encoding="ut...'
i managed to start B only when i 'drain'ed the contents of Q2
any hints of what i might be doing wrong when starting up the failed node?
Were there any core files generated? Send me the logs (of both nodes) and I'll
take a look.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
