once a message is acknowledged (acked) by a consumer and the broker received that ack, it is removed. What ack mode is in use by your consumer?
for topics there is an extension, retroactive consumer, that can allow replay of earlier messagers but this is not enabled by default. On 11 September 2012 12:39, Raj <raja.vedamoor...@yahoo.com> wrote: > Hello guys > > I just want to know, if there is a way to remove messages from queue/topic > (Enqueued Messages) once the Consumer ( MessageListener) receives the > message? > > I need this because, the MessageListener is picking up the earlier published > messages. Thank you. > > Raj > > Sent from my iPhone > > On Sep 8, 2012, at 11:45 AM, Raja vedamoorthy <raja.vedamoor...@yahoo.com> > wrote: > >> Thank you Gary I will check. >> >> --- On Fri, 9/7/12, Gary Tully <gary.tu...@gmail.com> wrote: >> >> From: Gary Tully <gary.tu...@gmail.com> >> Subject: Re: #AMQ-3353: Durable subscribers on durable topics don't receive >> messages after network disconnect >> To: users@activemq.apache.org >> Date: Friday, September 7, 2012, 5:58 AM >> >> There is reference to a unit test in that jira >> (https://issues.apache.org/jira/browse/AMQ-3353), does it correctly >> reflect your use case and the issue. >> >> the test is: >> https://issues.apache.org/jira/secure/attachment/12485386/DurableSubscriberWithNetworkDisconnectTest.java >> >> If it does, then please reopen the issue and we will try and get to it for >> 5.7 >> >> Note: >> With dynamicOnly=true, a durable sub is recreated by the bridge when >> there is new demand, so when a remote durable sub registers again. >> With dynamicOnly=false, a durable sub is recreated on bridge startup, >> so that messages flow to the remote broker irrespective of connected >> consumers. >> >> >> On 7 September 2012 11:13, Andreas Calvo <andreas.ca...@scytl.com> wrote: >>> Wrong link: https://issues.apache.org/jira/browse/AMQ-3353 >>> >>> El vie 07 sep 2012 11:57:12 CEST, Andreas Calvo escribió: >>> >>>> Hi, >>>> We are still affected by this issue. >>>> >>>> Taking a look at the code, it seems that upon undesired disconnection >>>> and reconnection, all durable subscribers affected are lost. >>>> Using JMX we're able to see how the NC is lost and not successfully >>>> recreated. >>>> >>>> However, we've identified that even standalone brokers in a NoB are >>>> affected by this issue, and did do not successfully reconnected to >>>> each other. >>>> >>>> I'll try 5.7-SNAPSHOT, but we've been following this issue since 5.5 >>>> and now it's marked as resolved. >>>> >>>> Link: https://issues.apache.org/jira/browse/AMQ-3393 >>>> >>> >>> -- >>> Andreas Calvo Gómez >>> Systems Engineer >>> Scytl Secure Electronic Voting >>> Plaça Gal·la Placidia, 1-3, 1st floor · 08006 Barcelona >>> Phone: + 34 934 230 324 >>> Fax: + 34 933 251 028 >>> http://www.scytl.com >>> >>> NOTICE: The information in this e-mail and in any of its attachments is >>> confidential and intended solely for the attention and use of the named >>> addressee(s). If you are not the intended recipient, any disclosure, >>> copying, >>> distribution or retaining of this message or any part of it, without the >>> prior >>> written consent of Scytl Secure Electronic Voting, SA is prohibited and >>> may be >>> unlawful. If you have received this in error, please contact the sender >>> and >>> delete the material from any computer. >> >> >> >> -- >> http://fusesource.com >> http://blog.garytully.com -- http://fusesource.com http://blog.garytully.com
