qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joshua Braegger <rckcl...@gmail.com>
Subject Clustered broker fails to correctly rejoin cluster
Date Thu, 30 Apr 2009 19:14:11 GMT
I've been using qpid for the last couple of days, have been testing failure
scenarios, and had a question about a side-effect I've been having -- I'm
wondering if it's a bug or if I'm doing something wrong.

First, let me explain what I am doing.  Basically, I start a cluster --
brokerA and brokerB, create an exchange/queue, and have a consumer poll
brokerA for messages.  Then I kill brokerB, and start it back up again.  It
joins the cluster fine.  However, when I attempt to send messages to brokerA
and brokerB from my producer, brokerB dies and I get the following output on
brokerB (startup to shutdown):

2009-apr-30 15:09:47 notice Recovering from cluster, no recovery from local
2009-apr-30 15:09:47 notice SASL disabled: No Authentication Performed
2009-apr-30 15:09:47 notice Listening on TCP port 5678
2009-apr-30 15:09:47 notice joining cluster foo
with url=amqp:tcp:
2009-apr-30 15:09:47 notice Broker running
2009-apr-30 15:09:47 notice caught up, active
cluster member
2009-apr-30 15:10:14 error Channel exception: not-attached:
session.completed: channel 0 is not attached
2009-apr-30 15:10:14 critical Error 57 did
not occur on
2009-apr-30 15:10:14 error Error delivering frames: Aborted by local failure
that did not occur on all replicas
2009-apr-30 15:10:14 notice leaving cluster
2009-apr-30 15:10:14 notice Shut down

brokerA remains running fine.

I'm using CentOS 5.3.  Let me know if any more information would be helpful

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message