RE: [Dispatch Router] amqp:not-found
Thanks Gordon, it works perfectly! Olivier -Original Message- From: Gordon Sim Sent: lundi 17 septembre 2018 12:23 To: users@qpid.apache.org Subject: Re: [Dispatch Router] amqp:not-found On 17/09/18 10:52, VERMEULEN Olivier wrote: > Hello, > > Our messaging topology uses a dispatch-router in front of a bunch of brokers > (the Java one). > Note that we never use the dispatch-router for direct communication between a > producer and a consumer, everything goes through a broker. > Now when we try to send a message, through the dispatch-router, to a topic > that does not exist on the brokers the send just hangs whereas I would expect > an amqp:not-found exception... > From what I understood from my readings this is currently expected because > the dispatch-router is creating an address locally and waits for a consumer > to connect to it. > Would it be possible to make this behavior configurable, if not already done? You can set defaultDistribution to unavailable in the router section of the config. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org *** This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorised to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [Dispatch Router] amqp:not-found
On 17/09/18 10:52, VERMEULEN Olivier wrote: Hello, Our messaging topology uses a dispatch-router in front of a bunch of brokers (the Java one). Note that we never use the dispatch-router for direct communication between a producer and a consumer, everything goes through a broker. Now when we try to send a message, through the dispatch-router, to a topic that does not exist on the brokers the send just hangs whereas I would expect an amqp:not-found exception... From what I understood from my readings this is currently expected because the dispatch-router is creating an address locally and waits for a consumer to connect to it. Would it be possible to make this behavior configurable, if not already done? You can set defaultDistribution to unavailable in the router section of the config. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
[Dispatch Router] amqp:not-found
Hello, Our messaging topology uses a dispatch-router in front of a bunch of brokers (the Java one). Note that we never use the dispatch-router for direct communication between a producer and a consumer, everything goes through a broker. Now when we try to send a message, through the dispatch-router, to a topic that does not exist on the brokers the send just hangs whereas I would expect an amqp:not-found exception... >From what I understood from my readings this is currently expected because the >dispatch-router is creating an address locally and waits for a consumer to >connect to it. Would it be possible to make this behavior configurable, if not already done? Thanks, Olivier *** This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorised to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system.
