Hey Michael, it turns out that the activemq broker actually does not
proactively purge expired messages from queues. The broker will not send
expired messages to consumers, but if there are no consumers consuming from
the queue, expired messages just sit.
Today I made a similar post:
http://w
Non persistent messages are gradually being produced into a queue with some
TTL. The message consumer application is down or cannot access the activemq
broker. How do I purge expired messages? It turns out that without a
consumer, the broker will not proactively purge expired messages
(https://
Attached is the program which can be used to reproduce the issue. This uses
the .binding files to interact with ActiveMQ.
http://www.nabble.com/file/p22745175/TestAMQGetMsg.java TestAMQGetMsg.java
ManojC wrote:
>
> One more thing I noticed in the stack is that there is thread in MQ which
> neve
Hello,
I have just rerun the testcase against the latest trunk and the
problem does not occur anymore. I have let the test run
for about a million messages.
Ig you have time, perhaps you can double check this ?
Best regards
Andreas
On Mar 26, 2009, at 5:41 PM, Andreas Gies wrote:
Hi ther
Thanks Gary for the suggestions.
I was able to get a working code. Sharing the same for review as well as for
others.
ConnectionFactory factory = (ConnectionFactory) ctx.lookup(FACTORY_NAME);
System.out.println("Lookup succesfull " +
factory.toString());
Hi,
can you create a reproducible test case of this issue?
Cheers
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Fri, Mar 27, 2009 at 12:53 AM, ManojC wrote:
>
> Hi
> We are using JAVA P
Gary,
I have attached the test case as you asked.
Is there any other way I can help to resolve this issue?
Regards,
Jarek
W dniu 26 marca 2009 23:59 użytkownik Gary Tully napisał:
> Hi Jarek,
> great that it reproduced easily. That test case should be fine.
> I have created a jira issue to tra
