No that large : 360 messages of average size of less than 1Ko.
I did not check the heap at the time of the event. I'll take a look at
those next time ...
But do you think Jetty can have keep ActiveMq from shutting down ?
On Thu, Jul 3, 2014 at 5:58 PM, Christian Posta christian.po...@gmail.com
I ran into the same issue. The good thing is I figured out what was causing
the issue. I believe the issue is two issues. There is a deadlock in the
processing of async jobs that is blocking a job that can unblock the
deadlock.
The two threads that are important are:
Thread 43139: (state =
Hi,
I am using ActiveMQ 5.8 and trying to switch to ActiveMQ 5.10. The problem
here is that I have to clear the kahaDB before switch otherwise I get error.
This also happens if I want to switch back from 5.10 to 5.8.
Everytime we need to clear the kahaDB
Error:
java.io.IOException: Could
That is not good. We try and do auto updates - the test is at
https://github.com/apache/activemq/blob/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/store/kahadb/KahaDBVersionTest.java
I wonder what is different in your store?
You could just rebuild the index, use forceRecoverIndex
I'm trying to use the REST API to GET a response from a queue.
I set my url to :
http://appdev003:8161/api/message/xml2test.replyto.queue?type=queueclientId=XML2TestreadTimeout=1000
I added a header for selector:
JMSCorrelationID='9595bb66-6fb7-4f6f-8bd5-ff86721f35f7'
I checked the message and
