We have been able to localise the problem I think. Seems that there were very
little memory available outside of the JVM available for the OS. After
making sure that there are more free memory we have not seen the problem ..
Thanks for your effort!
--
Sent from: http://activemq.2283324.n4.
I can understand that, however, we're pretty much stuck with this version for
different reasons. I was just hoping for someone to recognise problem and to
chip in.
I guess it can also be valuable for other users stuck on 5.6.0, if there are
any, to post my findings here.
The thread- OOM causing
I logged the size of the write this time. We crashed just after trying to
allocate 26MB. Is that considered to be much? Looking at the total heap
usage at the time of the crash we seem far away from the max provided limit
of 2,5GB so seems strange to me.
--
Sent from: http://activemq.2283324.n4
By changing the code for the"ActiveMQ Data File Writer" - thread we found out
that we get an OOM:
java.lang.OutOfMemoryError
at sun.misc.Unsafe.allocateMemory(Native Method)
at java.nio.DirectByteBuffer.(DirectByteBuffer.java:120)
at java.nio.ByteBuffer.allocateDirect(Byte
Interesting observation. It seems that the "ActiveMQ Data File Writer"
thread, responsible for releasing the lock (if I understand the code
correctly), dies after while and soon after that the total freeze occurs.
Might be that we're hitting: https://issues.apache.org/jira/browse/AMQ-6688
?
I
I have added parts of it that I think is of most interest but I will try to
add all of it as well.
We have considered to upgrade but it will be a VERY cumbersome process for
us so it's kind of our last resort.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
sorry, introducing some new *connection* pools, not "thread pools"
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi!
Wen have a problem that we have been struggling with for a while.
Every now and then we experience total freezez of ActiveMQ. Producers can't
produce messages, consumers will not consume and we can't even browse the
queues using the web console when this occurs.
We're running ActiveMQ 5.6.
