Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Fri, 7 Feb 2014 22:21:56 -0800 (PST)
From: artnaseef <art@artnaseef.com>
To: users@activemq.apache.org
Message-ID: <215E2818-2868-409E-8BF6-D93BC064EE7D@artnaseef.com>
In-Reply-To: <201402081003072163681@gmail.com>
References: <1391808313384-4677644.post@n4.nabble.com>
 <201402081003072163681@gmail.com>
Subject: Re: Runaway producer: Proper way to clean up a topic?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_96485_11889030.1391840516939"

------=_Part_96485_11889030.1391840516939
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Perhaps persistence isn't needed for those messages at all. 30 seconds is bordering on too fast to restart a broker in many cases. 

With that said, it sounds like there may be at least one bug here. If a junit case can be written to prove this case, that would help a lot.  Alternatively, a minimal client that demonstrates the problem would help. 

Sent from my iPhone

> On Feb 7, 2014, at 7:04 PM, "kimmking [via ActiveMQ]" <ml-node+s2283324n4677654h22@n4.nabble.com> wrote:
> 
>  
> Use deleteAllMessagesOnStartup option: 
> https://activemq.apache.org/broker-uri.html
>  
>  
> From: [hidden email]
> Date: 2014-02-08 05:26
> To: [hidden email]
> Subject: Runaway producer: Proper way to clean up a topic?
> In a previous post I described a problem that occurred in a jdbc-backed 5.9.0 broker with a durable subscriber.  The producers got way ahead of the consumer (which disconnected though did not unsubscribe).  I had to restart activemq as it was hung. 
> 
> The messages in the topic had a 30 sec expiration so they were all well expired by then. 
> 
> I had hoped that when I restarted the broker it would clear out the ACTIVEMQ_MSGS table, as all the records were expired.  Nope. 
> 
> However, an activemq timer thread slowly started cleaning up the records, 1 per second.  At that rate it was going to take 87 hours to clean them all out! 
> 
> I then used the console to destroy the durable subscription, thinking that would accelerate the process. Nope.  In fact the 1 second timer ceased functioning. 
> 
> At this point I deleted the records by hand using SQL. 
> 
> What did I do wrong?  What would be the correct way to clear out the topic in the event of such a scenario? 
> 
> Thanks 
> John 
> 
> 
> 
> 
> 
> If you reply to this email, your message will be added to the discussion below:
> http://activemq.2283324.n4.nabble.com/Runaway-producer-Proper-way-to-clean-up-a-topic-tp4677644.html
> To unsubscribe from ActiveMQ - User, click here.
> NAML
> 
> 
> If you reply to this email, your message will be added to the discussion below:
> http://activemq.2283324.n4.nabble.com/Runaway-producer-Proper-way-to-clean-up-a-topic-tp4677644p4677654.html
> To start a new topic under ActiveMQ - User, email ml-node+s2283324n2341805h3@n4.nabble.com 
> To unsubscribe from ActiveMQ - User, click here.
> NAML


--
View this message in context: http://activemq.2283324.n4.nabble.com/Runaway-producer-Proper-way-to-clean-up-a-topic-tp4677644p4677655.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
------=_Part_96485_11889030.1391840516939--