Hi Martin,
Through your guidance and help. I was able to solve our message count
problem (plus no calls to core ActiveMQ classes)!
Many thanks again.
Kevin.
On Wed, Nov 30, 2011 at 11:13 AM, Martin C. wrote:
> Hi,
>
> as you are using queues, you don't have durable/non-durable
> subscriptions.
Hi,
as you are using queues, you don't have durable/non-durable
subscriptions. But it appears to me that you do NOT close the last
consumer, that's why the queue is not actually removed. You also
should NEVER need to interact with the persistence adapter.
Still, the issue is that you should NOT N
Hi,
I'm using ActiveMQQueues, that are not persisted. The subscriptions
are non-durable. I'm removing the queues from the JMX bean by calling
removeQueue (which succeeds, as they dis-appear when viewed with
JConsole) - However, when I look with a profiler, I still see
ActiveMQQueue instances layin
Hi,
first thing: does it occur while there is a consumer? Or only if there
is no consumer? Are you using queues or topics (maybe even with
persistent subscriptions)?
TTL basically works the way you expected, BUT it depends if the
messages are persistent or not, and if you have configured expired
Hi,
Many thanks for your reply. There is a possibility in my app that
messages can't be delivered (client has closed the browser). I was
looking for a mechanism whereby there would be some sort of timeout on
the message, say a couple of minutes and if it hadn't been delivered
then the broker can d
Hi,
if TotalMessageCount is not decreasing, this indicates that you are
either not consuming or maybe not committing the consuming transaction
/ not acknowledging the messages on the receiving side (depends on
your acknowledge mode).
Best regards,
Martin
On Tue, Nov 29, 2011 at 4:39 PM, Kevin Ki
Hi,
I seem to have a memory leak, in that messages seem to be hanging
around in the broker. Using JMX I can see that the TotalMessageCount
is not 0. Also, MemoryPercentUsage eventually gets to 100% and then
the app freezes, if I increase the MemoryLimit, then the app begins to
run again.
If I clo
