Hello,
> The JVM flags used are: ... -Xss1024m
Are you sure about that -Xss1024m? That would set the thread stack size to a
monstrous 1GB. Perhaps you wanted to configure the initial heap size (-Xms)
there but made a typo? If that's really what's configured there try to
remove it or modify it to -Xms1024m which is probably what was intended to
be set there. That could be all you need to do.
With 64-bit JVM you shouldn't be normally hitting the native memory
exhaustion issue unless the whole system is low on total memory available.
It was more common issue with 32-bit systems given the limited address
space.
But check the amount of RAM and monitor the memory usage (on the whole
system) as well, maybe you're operating close to the maximum available. In
such case you can either add more RAM to the system or decrease the maximum
heap size (Xmx) if that's acceptable (you can do that with another instances
as well - it's about lowering the total memory requirements). Or if there's
no other way, you can still try lowering the stack size a little - your
default is 1MB, so you may try something in the range: 768k - 896k.
Max processes limit looks high enough so that shouldn't be an issue.
You can monitor the count of threads for the user to verify that the limit
isn't being sometimes hit, something like the following example should be
usable (there might be better alternatives):
ps h -fLu username | wc -l
Best regards,
Petr
"It's at 64-bit system/JVM.
The process limits from /proc/pid/limits are:
Max processes 16341 16341
processes
Max open files 65536 65536 files
The JVM flags used are : -Xmx8g -Xss1024m
The default value in JVM is:
amq...@stokes31.toa(nyc):~> java -XX:+PrintFlagsFinal -version | grep
ThreadStackSize
intx ThreadStackSize = 1024
{pd product}
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
The OS limits and heap sizes seem more that enough to me. I have another
instance that runs with same configuration and hasn't exhibited this
behavior. What other factors should i look at for more information next time
this issue occurs.
How can i increase the native memory space if thats what is causing this?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
"
