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 30000ms. I already put maxInactivityDuration
on 0.

How can we resolve this? Is it a Mule error or is it a AMQ config error?
The error only occurs from a day apart.
The thing we try to do is have two channels forwarded from local to another
server through http.

Our activeMQ config is the following:


Thanks!



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Broker-already-connected-tp4665248.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to