we are getting the GC printed on to the same catalina.out and we see that the
memberAdded messages appear almost at the time of GB getting printed, does
it prove that longer GC pauses are causing this? is there any other data
points/proof can be get?
rearding network problems, we are requesting
nageshsrao wrote:
we are getting the GC printed on to the same catalina.out and we see that the
memberAdded messages appear almost at the time of GB getting printed, does
it prove that longer GC pauses are causing this? is there any other data
points/proof can be get?
E.g.
Hi,
In our prod environment we have two tomcat's [ 5.0.27] running on two linux
boxes [ RHAS 3.0 update8 ] and using mod_jk2.0 thru apache for accessing the
information.
very frequently we see the following messages in the catalina.out and there
are about 2 instances where tomcat stopped
You configured a 3 seconds timeout for your heartbeat. If a node doesn't
receive a heartbeat packet for 3 seconds, it assumes the other node is
dead and closes the incoming replication connection. If the other node
is not really dead, it will try to use this replication connection which
will
