Huh?
On Wed, 16 May 2018 at 10:19 pm, Twers1991 wrote:
> Its fixed, it doesnt appear such a issues, they work pretty well on it!
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
Its fixed, it doesnt appear such a issues, they work pretty well on it!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I hate trying to troubleshoot memory usage; it's nearly impossible to do
well, especially after the fact. It's very hard to tell exactly what causes
the increase in memory.
When measuring memory, it's important to understand that top measures total
RAM, which 1) includes memory that's not on the h
Sorry about the no response, I was monitoring and since we increased the
memory to 4Gb we hadn't seen an issue until two days ago. The memory use I
found was from top, the lab result we got where it "hung" hasn't happened
again, I'm not sure what else was at play there.
Two days ago we had an inst
Sorry, I quoted you as saying "unresponsive" but your actual word was
"hung."
On Fri, Apr 6, 2018, 7:13 AM Tim Bain wrote:
> 1GB sounds a little small for that volume, especially if there is any
> danger of some consumers of durable topics being offline for a while, or of
> all consumers on a gi
1GB sounds a little small for that volume, especially if there is any
danger of some consumers of durable topics being offline for a while, or of
all consumers on a given queue being offline. Either way, you've proven
that 1GB isn't enough, by hitting an OOM. The fact that you haven't hit it
till n
Great stuff - thanks Gary! :)
2008/8/28 Gary Tully <[EMAIL PROTECTED]>:
> trying to pull this information together, there is some more detail
> at: http://activemq.apache.org/javalangoutofmemory.html
>
> 2008/8/27 James Strachan <[EMAIL PROTECTED]>:
>> Try increase your heap; as a broker and mule
trying to pull this information together, there is some more detail
at: http://activemq.apache.org/javalangoutofmemory.html
2008/8/27 James Strachan <[EMAIL PROTECTED]>:
> Try increase your heap; as a broker and mule server and JMS client is
> gonna use up RAM.
>
> To reduce the memory overhead of
Try increase your heap; as a broker and mule server and JMS client is
gonna use up RAM.
To reduce the memory overhead of the JMS client you can reduce the prefetch...
http://activemq.apache.org/what-is-the-prefetch-limit-for.html
the out of the box broker config should be fine but if you're reall
Hi,
We are using following -
1. ActiveMQ 5.1
2. I have not set JVM heap to any value.
3. We are running a mule server.
4. Both the consumer and broker are using the same JVM.
Thanks,
Manu
James.Strachan wrote:
>
> Which version are you using? What did you set your JVM heap to? Which
> JVM got
Which version are you using? What did you set your JVM heap to? Which
JVM got the OOM exception, the broker or the consumer?
This document helps you get better help quicker
http://activemq.apache.org/support.html
2008/8/27 Manupriya <[EMAIL PROTECTED]>:
>
> Hi,
>
> We have the following requireme
11 matches
Mail list logo