A new JIRA tracker has been created for this issue:
https://issues.apache.org/activemq/browse/AMQ-1876
/x. n. busly
Mike Gallaher wrote:
>
> Aaron Pieper posted a message yesterday in another thread that gives more
> details, but the nutshell version is that the topic only starts to
> accumula
I was able to avoid the problem by setting pubSubNoLocal on my consumer to
false.
Presto, the topics no longer leak memory.
It was and is using AUTO_ACK.
I'm using a Spring SimpleMessageListenerContainer on the consumer side, but
a client using raw JMS primitives behaves the same way.
Aaron Piep
I'm not sure if it will help, but you could try disabling producer
flowControl:
It would also be interestin
I forgot to mention that I am running 5.1.0.
I'll try the latest snapshot, but as we're about to release our project I'd
rather use a release version of ActiveMQ if possible. Writing
non-persistent messages to a topic is such a basic use case that I thought I
must be doing something wrong, but
Re #1, see the following JIRA
https://issues.apache.org/activemq/browse/AMQ-1600
I am using AMQ 5.1, with a similar setup and except for the QueueSize issue,
everything seems to run okay for me. It sounds like there is a problem with
how the messages are being acknowledged.
I'd upgrade to 5.
Topic's QueueSize and MemoryPercentUsage grow until the latter hits 100%,
and then no messages are delivered to consumers on the topic.
I'm having this same problem. It's a showstopper for us.
Why is a topic accumulating anything whatsoever? The messages aren't
persistent and have 5 second tim
