[rabbitmq-discuss] ShutdownListener

cw storm cwstorm at gmail.com
Fri Feb 14 22:06:39 GMT 2014


Does anyone have a good practice to manage subscription to a queue in the
event the rabbit server was restarted?


On Fri, Feb 14, 2014 at 4:40 PM, cw storm <cwstorm at gmail.com> wrote:

> Actually, it should be "*handleShutdownSignal" not "ShutDownCompleted"*
>
>
> On Fri, Feb 14, 2014 at 4:38 PM, cw storm <cwstorm at gmail.com> wrote:
>
>> Thanks for the confirmation.  So you mean I need to implement the below
>> like this in my consumer:
>>
>> channel.basicConsume(strQueueName, false, strConsumerTag,
>> new DefaultConsumer(channel) {
>>                         public void
>> shutdownCompleted(ShutdownSignalException cause)
>>      {
>>                                             // handle scenarios
>>
>>                                  }
>>
>>
>> On Fri, Feb 14, 2014 at 4:28 PM, Michael Klishin <mklishin at gopivotal.com>wrote:
>>
>>>
>>> On 15 Feb 2014, at 01:24, cw storm <cwstorm at gmail.com> wrote:
>>>
>>> > "will trigger a shutdown in the Java client."
>>> >
>>> > Are you referring to the "ShutDownSignalException" block?
>>>
>>> The process described in http://www.rabbitmq.com/api-guide.html#shutdown
>>> ,
>>> which will call shutdown listeners for connections, channels and
>>> consumers that
>>> have them.
>>>
>>> MK
>>>
>>> Software Engineer, Pivotal/RabbitMQ
>>>
>>>
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140214/d3e329f3/attachment.html>


More information about the rabbitmq-discuss mailing list