[rabbitmq-discuss] Problem: NOT_FOUND - no binding between exchange 'xxxxx' in vhost

Fri May 9 15:07:59 BST 2014

Unfortunately there's not much to go on here, but this does sound like 
it has some features in common with a bug we fixed in 3.2.0. So if 
anyone sees this behaviour with >= 3.2.0 I would be very interested to 
hear about it, but otherwise I am inclined to leave it.

Cheers, Simon

On 08/05/14 21:32, Scott Durgin wrote:
> Thanks, yes, we’ve done that… we’re testing now; that said, it would be
> nice to know what the cause of the problem was because when I am in
> production this kind of service disruption would be incredibly painful
> (and kill my SLAs).
>
> Appreciate any additional perspectives.
>
> Thanks
>
> *From:*rabbitmq-discuss
> [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] *On Behalf Of
> *Laing, Michael
> *Sent:* Thursday, May 08, 2014 2:02 PM
> *To:* Discussions about RabbitMQ
> *Subject:* Re: [rabbitmq-discuss] Problem: NOT_FOUND - no binding
> between exchange 'xxxxx' in vhost
>
> The first thing to do is to upgrade that old rabbit. -ml
>
> On Thu, May 8, 2014 at 1:57 PM, Scott Durgin
> <sdurgin at presencenetworks.com <mailto:sdurgin at presencenetworks.com>> wrote:
>
> Using RabbitMQ 3.0.0
>
> No cluster
>
> Access via Spring Framework, RabbitMQ abstraction layer
>
> Running on Amazon EC2
>
> We’re using RabbitMQ for an event-driven “RFID Data in the cloud”
> solution, and at the core we use RabbitMQ as our messaging layer. It’s
> been pretty much set-and-forget (which is probably the biggest
> compliment I can give to the developer community -- so thanks to you and
> all the contributors for your efforts!).
>
> We are running into an issue with our implementation with the following
> error:
>
> NOT_FOUND - no binding between exchange 'TripEvent.COMPLETED' in vhost
> '/' and queue 'fpms' in vhost '/'
>
> We are dynamically creating bindings between exchanges and queues as
> part of an internal subscription event management function in our
> solution.  All of a sudden messages stop being delivered. When we go
> into the console, it shows all the bindings but when you go to unbind,
> we get the above error message.
>
> I wanted to see anybody might be able to point us in a certain direction
> to understand the core problem we have – configuration issue, calling
> something incorrectly, known issue with RabbitMQ, or something.
>
> Rabbitmq is so core to our solution, that not knowing why this is
> happening makes me very uncomfortable. We are about 4-5 weeks away from
> a production pilot, so of course this issue came about! J
>
> Appreciate any insight, assistance or direction anybody can provide!
>
> Thanks
>
> /Scott
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> <mailto:rabbitmq-discuss at lists.rabbitmq.com>
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

-- 
Simon MacMullen
RabbitMQ, Pivotal