Changing to the default for retries fixed our problem. I still have one question. How does retries > 1 work for a loadbalancer with sticky requests? A user started a session on a worker and got a jvmRoute to that worker in its session cookie. The worker fails and is put in error state. Will a sticky request for that worker be routed to another worker or will the request fail?
regards Henk Henk Fictorie wrote: > > Rainer, > > Thanks for your response. > You mentioned our setting of retries=1, so I reread the documentation to > find out that it actually means 'no retries'. I have now commented out > that line, so it will get the default value of 2. > It will let you know if it helped. > > regards Henk > -- View this message in context: http://www.nabble.com/mod_jk---connectionTimeout-en-connection_pool_timeout-tf4390617.html#a12591428 Sent from the Tomcat - User mailing list archive 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]
