Hi,
Even after changing my settings to a hung node A still does not failover to
node B. The whole server is hung.
worker.loadbalancer.lock=P # P[essimistic]
Any more recommendations?
Thank you,
Vidya
--
View this message in context:
The directive :
disabled - If set to True or 1 the worker will be disabled if member of load
balancer. This flag can be changed at runtime using status worker.
Can I change the disabled property at runtime and will the loadbalancer be
able to read this? I tried changing it in worker.properties
hi
we has similar issue
we did not mess with prepost values but changed
locking method to pesimistic, and set socket_timeout to 60sec, recycle_time
to 600sec and reply_timeout to 18(ms)
these were recommended by Mladen Turk and now Busy connections are
distributed among all nodes equally.
Our application which runs on Apache HTTP Server 2.0.54, TOMCAT 5.0.28 with
mod_jk 1.2.15 connector. In production while our application was running.
Our application had a thread dead Lock hosing up all the users trying to
connect our application. So started investigating the failover setup in