Is there noone with an idea?
I've made a new graph with a longer timeperiod:
http://achelois.tweakers.net/~acm/tnet/long-activemq-gc.png
For now we can only fix this by periodically restart ActiveMQ, but
that's not a very nice aproach.
Best regards,
Arjen
Arjen van der Meijden wrote:
Hi li
Hi list,
Currently we're seeing some strange behaviour from ActiveMQ 5.0 (release
version).
In our set-up we have one ActiveMQ instance with four queues on it and
all communication with AMQ is via the Stomp-interface. Although we
cleaned the activemq.xml a bit, we basically left all settings
