-none- 2007-08-14 - By Rainer Jung
Back
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 not work any more.
Why could this happen: one possible reason are GC pauses. If you've got
longer GC pauses, than your membership heartbeat timeout, then you run
into such problems.
During normal operations you should not observe any memberDisappeared
messages. They should only show up, ehen you stop a node or it crashes,
or you've got serious network problems with impact on the multicast
heartbeat packets.
If you decide to increase the membership timeout (which sounds like a
good idea), keep in mind, that you need to wait the given time between
stopping and restarting a node.
Regards,
Rainer
nageshsrao wrote:
> 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 responding and we had to restart.
> the only errors that we see are the following.. There are INFO which keeps
> telling us member is disappeared and added and once in a while we have
> SEVERE messages.
>
> Could you let us know, what could be causing this problem? is there any
> additional configuration that are needed?, This environment is running for
> almost 18 months in production and off-late [ in the last 6 months] we have
> seen this happenned twice. I have attached both the error log found in the
> catalina.out and also the server.xml from both the tomcat.
>
>
> http://www.nabble.com/file/p12142134/catalina-error.out catalina-error.out
> http://www.nabble.com/file/p12142134/server-app1.xml server-app1.xml
> http://www.nabble.com/file/p12142134/server-app2.xml server-app2.xml
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
