[rabbitmq-discuss] Send problem (receiver closes exchange)

Bernhard Mogens Ege bme at saseco.dk
Mon Mar 25 15:57:36 GMT 2013

I'll answer my own blunder... the exchange was set to autodelete and only the subscriber was listening for messages from it. The sender only sent messages but had not other handle on it. :-P


From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Bernhard Mogens Ege
Sent: 25. marts 2013 16:51
To: rabbitmq-discuss at lists.rabbitmq.com
Subject: [rabbitmq-discuss] Send problem (receiver closes exchange)

I am having two AMQP clients, one sends and another receives. I can start the sender without the receiver and while there is no receiver to receive the messages, the sender doesn't error. Then I start the receiver and then I receive messages as intended. But when I stop the receiver, the sender throws exception on each message sent:

RabbitMQ.Client.Exceptions.AlreadyClosedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=404, text="NOT_FOUND - no exchange 'coma.event' in vhost '/'", classId=60, methodId=40, cause=

Is it possible for one client to close an exchange that another client is actively using?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130325/9db01e96/attachment.htm>

More information about the rabbitmq-discuss mailing list