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:
What garbage collection strategy are you using? CMS has a potential failure
mode where due to memory fragmentation it can be unable to allocate a large
memory chunk even though there's more than that free, so I'd recommend G1
if you're on a recent JVM (7 or later) or Parallel if you're on an older
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
If you want help you are going to need to upgrade to a supported version.
There have been over 4200 commits since 5.6.0 so no one is going to try and
debug a version that old when the issue may have been fixed years ago.
On Thu, Apr 4, 2019 at 8:11 AM mcrandy wrote:
> I logged the size of the
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:
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
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
The thread dump didn't make it into your message. Can you please re-send it?
Also, does this problem occur if you upgrade to a version of ActiveMQ that
was released recently? 5.6.0 is nearly seven years old, and there's not
much appetite for debugging hard-to-reproduce problems in old software.
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
Source Integration
http://fusesource.com
--
View this message in context:
http://old.nabble.com/ActiveMQ-freeze-tp28581838p28607920.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
--
View this message in context:
http://old.nabble.com/ActiveMQ-freeze-tp28581838p28607920.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
there?
Hope somebody can help.
Best,
Andreas
--
http://blog.garytully.com
Open Source Integration
http://fusesource.com
--
View this message in context:
http://old.nabble.com/ActiveMQ-freeze-tp28581838p28607920.html
Sent from the ActiveMQ - User mailing list archive
://blog.garytully.com
Open Source Integration
http://fusesource.com
--
View this message in context:
http://old.nabble.com/ActiveMQ-freeze-tp28581838p28607920.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://blog.garytully.com
Open Source
Hello,
currently I have an ActiveMQ 5.4-SNAPSHOT running for a test. It is as pure
master-slave configured.
Last Friday the whole system stopped working I mean no new messages were
enqueued, no messages were dequeued. No exception was thrown, no warning,
nothing. It just stopped working
If you can capture some thread dumps of both the master and slave brokers,
ideally a small series, with few seconds between each this would help
determine what is going on.
Obviously, if this is repeatable, please open a jira issue to track it and
add your test case if you can.
On 17 May 2010
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas,
did you create a thread dump of the (active) broker process?
Glück auf,
Dirk
Andreas Prüller wrote:
Hello,
currently I have an ActiveMQ 5.4-SNAPSHOT running for a test. It is as pure
master-slave configured.
Last Friday the
18 matches
Mail list logo
