[rabbitmq-discuss] librabbitmq faults

Matthias Radestock matthias at rabbitmq.com
Mon Apr 16 16:18:50 BST 2012


On 11/04/12 10:29, Matti Linnanvuori wrote:
> I saw the following RabbitMQ server log entries when a Perl
> Net::RabbitMQ client got stuck in recv and did not receive messages
> that were sent to the queue that it is was consuming. The logging
> stopped and started again only later after ERROR REPORT, which seems
> to indicate some kind of error.
> [...]
> =ERROR REPORT==== 11-Apr-2012::10:39:02 === connection<0.260.0>,
> channel 1 - error: {amqp_error,not_found,"no exchange
> 'exchange.pmc.email-in' in vhost '/'", 'basic.publish'}

That error message is pretty clear as to what "kind of error" occurred: 
the client tried to publish a message to an exchange that doesn't exist.

In AMQP such errors will result in the channel getting closed by the 
server. I know nothing about the C client, but depending on how it 
handles this server-initiated channel closure handshake, that might be 
the reason for why you see the client getting stuck.



More information about the rabbitmq-discuss mailing list