I am trying to make sure my application is resilient. It sends JMS messages to
a remote ActiveMQ broker. Unfortunately when that broker goes down the client
starts to block even though I am using the Camel asyncSendBody method. See
below for the stack trace.
The ActiveMQ version is 5.3.0 althou
Hi all,
Im trying to use ActiveMQ with IPV6 but Im running into some problems. I'm
in debian linux, and seems that ActiveMQ(5.5.1) is up and listening IPV6.
tcp6 0 0 :::61616 :::* LISTEN 24671/java
I can make a ping and a telnet to ::1 61616 and all seems that works fi
Hi,
did you set all the active mq client libs in the CLASSPATH of the client?
Furthermore you have to add a jndi.properties file to your CLASSPATH.
For further information try http://activemq.apache.org/jndi-support.html
http://activemq.apache.org/jndi-support.html
--
View this message in cont
Hi,
did you also increase the -XmX parameter in the activemq startup script?
This can also be due to a problem in the client implementation - i.e.
transaction handling.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Usage-Manager-memory-limit-reached-tp4557657p4561328.h
You need to understand how much memory is being used, and by what.
Then you can see if you actually need more memory, or if you need e.g. to
define some message eviction policy.
For example, you could have a queue, where consumption does not keep up with
production.
Where is the memory being use
Section 4.4.10 of the JMS spec [1] is worth a look:
"JMS clients need to understand when they can depend on message order and
when they cannot."
I suggest you put full logging on in the broker and share with us the 10
seconds around your first out-of-order message.
I presume you are producing al
