Hi Everyone,
Can anyone please help me to give some solution on below error?
I am getting this error after every 2-3 Hours.
My activeMQ configuration is as follow.
ActiveMQ configuration is as follow:
ACTIVEMQ_OPTS="$ACTIVEMQ_OPTS_MEMORY -Xms1g -Xmx1g"
and activemq.xml configuration as follow:
Hi @Tim Bain
Can you please tell me how to enable the PFC in ActiveMQ?
Can we pass some VM arguments to enable it? If Yes then which file should
have those VM arguments.?
Thank You
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On Thu, Mar 15, 2018 at 1:45 AM, sathish.cre...@gmail.com <
sathish.cre...@gmail.com> wrote:
> Thanks a lot for your reply Tim,
>
> Below is the metrics details i grabbed from the server.
> ActiveMQ:
> 5.15.0
> non-persistent
> Running consumer -> singleton -> onMessage() -
Thanks a lot for your reply Tim,
Below is the metrics details i grabbed from the server.
ActiveMQ:
5.15.0
non-persistent
Running consumer -> singleton -> onMessage() -> submit callables ->
callables send updated message to destination
messages -> 600/hour
me
1. http://activemq.apache.org/producer-flow-control.html, and yes, you
should enable it. You should protect the broker (by preventing messages
from over-filling its heap) first and foremost, and PFC does that.
2. When you're out of memory, it tends to manifest itself all over the
place. There's no
Hi artnaseef,
i am facing same issue in my startup log after 5 days, similar to this,
Exception in thread "ActiveMQ InactivityMonitor Worker" Exception in thread
"pool-3-thread-121233" Exception in thread "pool-1-thread-1" Exception in
thread "pool-3-thread-432434" java.lang.OutOfMemoryError: GC
Check first for slow consumption.
Is producer-flow-control enabled on the broker? And, if it is, what is the
per-queue memory limit and the overall system limit.
The most common cause of Out Of Memory on ActiveMQ is a broker without
producer-flow-control and slow consumption, which mimics a memo
i am using ParallelGC (the default garbage collector)
here is some information :
XX:InitialHeapSize=262927424 -XX:MaxHeapSize=4206838784
-XX:+PrintCommandLineFlags -XX:+UseCompressedOops -XX:+UseParallelGC
--
View this message in context:
http://activemq.2283324.n4.nabble.com/java-lang-OutO
First, for a question about GC problems, you should probably tell us what
GC strategy you're using, and why you chose it.
Second, you made the claim that "to increase the memory to 2Gb ... only
delaying the issue from happening," which implies that you believe you're
running out of memory because
