I pretty much use the same configuration. Except that mod_jk doesn't detect a
hung application, but it does recognize a hung tomcat.
The workaround I have for the time being. I have a separate monitor program
which detects the hung application and then it modifies which is the active
node using
Finally figured how to use this:
httpd.conf:
JkMount /jkstatus/* status
worker.properties:
worker.list=loadbalancer,status
worker.status.type=status
URL:
http://localhost/jkstatus/
--
View this message in context:
http://www.nabble.com/mod_jk-disabled-directive---how-to-change-at-run
For several days now I have been trying various options in mod_jk including
the following. But I am unable to get apache mod_jk to detect a hung a node
due to a thread deadlock and failover to nodeB.
# below are in seconds worker.nodeA.cache_timeout=60
worker.nodeA.socket_timeout=30
worker.nodeA
Definition of disabled directive in
http://tomcat.apache.org/connectors-doc/config/workers.html
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
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:
http://www.nabble.com/question%3A-mod_jk-failo
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,
Thank you very much for the response. In my properties I have three
prepost_timeout properties set up. I changed the
loadbalancer.prepost_timeout from 5 to 5000 but this still did not help.
Meaning loadbalancer worker still did not recognize a hung app server nodeA.
worker.loadbalancer.pre
Hi,
Thank you for the response. I tried setting the acceptCount to 10 on the
nodeA which is main node. But even after more that 10 simultaneous user
request it did not failover to my nodeB.
This is what I did :
Thank you,
Vidya
--
View this message in context:
http://www.nabble.com/ques
Hi,
This is the first time I am posting a question here on this site. Is this
the approach to post a question? In which case how long does it usually take
to have a response to the question.
Thank you,
Vidya
--
View this message in context:
http://www.nabble.com/mod_jk-failover-loadbalancing-
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
mod
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
mod
11 matches
Mail list logo