Re: mod_jk failover and preferring localhost
That explains it, thanks. I've just set the lbfactor extremely high on the localhost in the interim to get mod_jk to prefer it over remote tomcats. -Todd -- View this message in context: http://www.nabble.com/mod_jk-failover-and-preferring-localhost-t1825380.html#a4980806 Sent from the Tomcat - User forum at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk failover and preferring localhost
Filip, we're not using sessions so we don't need sessions affinity, but if we did we'd use session replication rather than sticky sessions. The sticky option does accept true/false according to the documentation http://tomcat.apache.org/connectors-doc/config/workers.html . I think that's all unrelated to the issue we're seeing though which is that mod_jk seems to be completely ignoring the distance parameter. -Todd -- View this message in context: http://www.nabble.com/mod_jk-failover-and-preferring-localhost-t1825380.html#a4980476 Sent from the Tomcat - User forum at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mod_jk failover and preferring localhost
We have 10 web servers with Tomcat's running on them and a mod_jk configuration to prefer the tomcat on localhost and only failover to another machine if the local one fails. This worked fine under our older mod_jk, however, we just upgraded to 1.2.15 and now it that the local_worker properties are no longer supported, it's load balancing every request. So I checked out the workers.properties options page: http://tomcat.apache.org/connectors-doc/config/workers.html and noticed the new distance option so that I can give localhost a distance of 0 and everything else a greater distance so that the load balancer should always prefer localhost. However, it seems to be ignoring the distance property completely and load balancing every request. Can anyone suggest what I might try to get it to always use the local tomcat for requests unless it fails: worker.list=tomcat worker.tomcat.type=lb worker.tomcat.socket_timeout=195 worker.tomcat.balance_workers=localhost,latin1,latin2,... worker.tomcat.sticky_session=False worker.localhost.port=8009 worker.localhost.host=localhost worker.localhost.type=ajp13 worker.localhost.lbfactor=1 worker.localhost.distance=0 worker.latin1.port=8009 worker.latin1.host=latin1 worker.latin1.type=ajp13 worker.latin1.lbfactor=1 worker.latin1.distance=1 worker.latin2.port=8009 worker.latin2.host=latin2 worker.latin2.type=ajp13 worker.latin2.lbfactor=1 worker.latin2.distance=1 Thanks, Todd -- View this message in context: http://www.nabble.com/mod_jk-failover-and-preferring-localhost-t1825380.html#a4979143 Sent from the Tomcat - User forum at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_jk error log
Hi Mladen, I'll upgrade to the latest mod_jk. I do have a timeout set as follows: Then in my workers.properties we have: worker.tomcat.socket_timeout=60 Does that look OK? -- View this message in context: http://www.nabble.com/mod_jk-error-log-t1519311.html#a4126407 Sent from the Tomcat - User forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
