Hey,
Currently we use got 3 AMQ's spread over 3 different machines. We got it
setup so that AMQ A forwards (selective channels) to B which consumes. After
consuming (by Mule) it gets put back into B and B forwards to C. This works.
We use the following settings (this for example is for machine A):
Hey,
Upon checking the logging from time to time I encounter the following
warning:
Our clients (two Mule ESB flows) sometimes also crash saying that ActiveMQ
hasn't responded for more then 3ms. I already put maxInactivityDuration
on 0.
How can we resolve this? Is it a Mule error or is it a
That worked. Thanks!
Maybe an idea that somebody adds this to the guides for noobs like me
--
View this message in context:
http://activemq.2283324.n4.nabble.com/http-transport-instead-of-tcp-tp4654580p4654590.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hey,
Currently I got a setup that I am satisfied with Using ActiveMQ 5.6..
However it's using TCP instead of the desired HTTP (for Firewall reasons).
When I change TCP into HTTP I get that a library is missing. Upon searching
I found that I need to move some jars from optional to the lib folder. I
