We were finally allowed to upgrade to Tomcat 5.5.27 and that seemed to have done away with the symptoms (I'm reluctant so say that upgrading fixed the problem, since I don't even know what it was in the first place ;-)
Thanks for the help, everyone. d. > The chunk length message seems pretty weird. Looks like a protocol > corruption. Those indicate, that you should really try a TC update. > Concerining your restriction "can't update before any other options are > exhausted": there will never be any other options exhausted. But after > some options are taken, the rest get more and more expensive, risky and > with a low chance of success. > >> To me this look likes some weird error condition in Tomcat has hit an >> obscure bug in JK whereby it doesn't clear the response buffer between >> retries. Has anyone encountered this issue before or is just willing >> to land a helping hand in troubleshooting? > > Not encountered this before, and I think noone reported a similar > observation. Concerning "retries": Could you provide your full > configuration (e.g. retries for an ajp13 worker is something very > different from retries of a load balancer worker). > > Regards, > > Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
