Stopping the consumers involves sending SIGTERM to them which could kill them in the middle of processing a message. Being able to suspend delivery would allow us to make sure they were no longer processing messages before we kill them. Granted, we can get around this problem by retrofitting the code to handle SIGTERM appropriately but this would have been the easier approach.
However, there may be other use cases for a "suspend delivery" feature. On 11/1/07, James Strachan <[EMAIL PROTECTED]> wrote: > On 01/11/2007, Roger Hoover <[EMAIL PROTECTED]> wrote: > > While rolling out new consumer code, we'd like to suspend the broker > > so that messages can be enqueued but not delivered. Once we've pushed > > the new code out and restarted the consumers, we want to resume > > message delivery. > > > > Is this possible with ActiveMQ? > > > > Any advice/info is appreciated. Thanks, > > Why not just stop the consumers, redeploy the code and restart them? > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source SOA > http://open.iona.com >
