What we use is (Solaris 8, Apache 2.0.55, mod_jk.1.2.15): worker.worker1.type=ajp13 worker.worker1.host=a.b.c.d worker.worker1.port=xyz worker.worker1.lbfactor=50 worker.worker1.cache_timeout=600 worker.worker1.recycle_timeout=600 worker.worker1.socket_timeout=62 worker.worker1.sticky_session=1 worker.worker1.prepost_timeout=30000 worker.worker1.recovery_options=0 worker.worker1.reply_timeout=600000 worker.worker1.retries=1
same for worker2, worker3, worker4 worker.lbworker.type=lb worker.lbworker.balance_workers=worker4,worker3,worker2,worker1 worker.lbworker.sticky_session=1 worker.lbworker.local_worker_only=0 worker.lbworker.retries=1 When a tomcat worker goes does, the worker enters the error state and traffic gets redirected to another worker. When the tomcat worker is restarted it will eventually be detected by mod_jk and traffic gets directed to it. Henk -- Henk Fictorie KPN.com phone: +31 70 3438362 mobile: +31 6 51379479 email: [EMAIL PROTECTED] -----Original Message----- From: Vidya TR [mailto:[EMAIL PROTECTED] Sent: dinsdag 28 maart 2006 0:28 To: users@tomcat.apache.org Subject: mod_jk 1.2.15 - is this a solution for High Availability Clustering? 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.recycle_timeout=60 # Advanced ping-pong options worker.nodeA.recovery_options=0 # below are in milliseconds worker.nodeA.prepost_timeout=5000 worker.nodeA.connect_timeout=5000 # under load it can take awhile to get a reply when doing an initial JSP compile worker.nodeA.reply_timeout=60000 I give up coming to a conclusion that mod_jk 1.2.15 is not a solution for High Availability Clustering. -- View this message in context: http://www.nabble.com/mod_jk-1.2.15---is-this-a-solution-for-High-Availa bility-Clustering--t1352358.html#a3619614 Sent from the Tomcat - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
