I'm experiencing an issue running ActiveMQ 5.2.0 where it unpredictably stops
processing messages after running for a few days (up to a week or two). A
stack trace shows up in activemq.log like so:
ERROR Service- Async error occurred:
javax.jms.ResourceAllocationException:
If you read the "instruction" page you will see the last sentence says:
"Timeouts on the failover transport are available since 5.3 version."
That caught me out too. Seems we're going to have to wait for 5.3 for that
one.
--
View this message in context:
http://www.nabble.com/connection-fail
What is this wrapper you are talking about?
I've never seen that "couldn't ping JVM" message so I'm not sure whether
this is the same issue or not.
--
View this message in context:
http://www.nabble.com/Options-for-preferring-stability-over-reliability-tp22852174p23384104.html
Sent from the A
Thanks for the quick response. We are running 2 instances of ActiveMQ - one
is running 5.1.0 and the other is running 5.2.0. The one running 5.1.0 runs
out of memory every now and then and all connected senders go nuts and we
see a *big* increase in CPU on the sender machines (possibly due to high
We are using ActiveMQ quite extensively at Last.fm and are experiencing a
number of issues related to the huge load we are putting on it (at peak
times up to thousands of messages per second). We are using it in a number
of different scenarios but our general use case is that we would much rather
