MassDosage wrote:
>
> 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.
>
>
>
ActiveMQ gets "shipped" with Java wrappers http://wrapper.tanukisoftware.org
its a way of daemonising java
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
I too am seeing an issue that activemq freezes completely, Im not sure if it
is under "heavy" load at the time.
I'm using it as a simple queue with one producer and one consumer.
Nothing appears in the logs and wrappers reports that it "couldn't ping JVM
for xx seconds" and restarts ActiveMQ. B
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
please post as much information as you can w.r.t number of topics, queues
and xml configuration. If you can produce a junit test case that
demonstrates the behaviour you are experiencing that would be fantastic.
Using systemUsage it should be possible to ensure memory is never exhausted
and messag
Hey There-
I'm not gonna be of much help off the bat but can certainly commiserate with
you. I'm trying to achieve the same goal with similar message loads and am
getting frustrated too.
Are you guys running multiple brokers using the network-of-brokers
configuration? What I'm seeing right n
