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-Availability-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]
