That was my thinking too. Id have just done that, but since it is the opposite of your original suggestion I thought id ask first :)
Robbie > -----Original Message----- > From: Aidan Skinner [mailto:[email protected]] > Sent: 09 August 2009 22:10 > To: [email protected] > Subject: Re: [RFC] [Java] QPID-2018 Clear queue doesn't clear acquired > messages which is a little confusing if that's all there is. > > On Sun, Aug 9, 2009 at 9:41 PM, Robbie > Gemmell<[email protected]> wrote: > > > Checks for undeleted messages could be made using this number along > with the before/after MessageCount, but of course general queue > activity during the process could cause such a check to reach the wrong > conclusion. In order to accurately report the number of messages not > deleted due to being in an acquired state a new > 'clearQueueAndReportNumAcquired' method would need to be added to > (Simple)AMQQueue, does that seem ok to everyone? The only real > alternative is to start using the return value of the existing method > in the MBean and have the console indicate how many messages were > deleted, rather than how many were not. Thoughts? > > Reporting how many were deleted seems reasonable to me, I don't see > much gain in introducing a new method to do something slightly > different. > > - Aidan > > -- > Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org > "A witty saying proves nothing" - Voltaire > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
