There were a contribution that included a servlet that does a basic
health check and could be used by load balancers
https://issues.apache.org/jira/browse/AMQ-2829
Maybe we can revive this effort and provide something with the distro.
Regards
--
Dejan Bosanac
--
Red Hat, Inc
Slightly off topic, but given that there are a number of reasons why you can
open a tcp socket but not have a usable daemon behind it, you probably want an
application monitor in your load balancer rather than just a tcp monitor.
You could use the same code in your monitoring system to implement
Yes, the load balancers are performing some kind on 'tcp probe' every 10
seconds which probably explains the exceptions.
I now need to determine if I need to fix the load balancer config or if I
can safely ignore the exceptions.
--
View this message in context:
http://activemq.2283324.n4.nab
Looks like something else tried to connect to ActiveMQ and then dropped. Do
your load balancer machines have some sort of ping that it sends out?
On Fri, Jan 4, 2013 at 3:58 AM, jliezers wrote:
> Hi,
>
> We're running ActiveMQ version 5.6.0 in a MASTER/SLAVE configuration on
> linux.
>
> ActiveM
