I'm still digging, but I thought I'd send this along to the mailing list while I try to decipher the mod_jk code.
We're using tomcat-connector 1.2.31 on apache 2.2.17 on a Linux system. Log file is at this URL: http://www.moonteeth.com/~dopey/tomcat/mod_jk.log <http://www.moonteeth.com/%7Edopey/tomcat/mod_jk.log> The worker configuration consists of a load balanced worker with 9 workers (tomcat1-9). At any given time, usually only one tomcat is in use. In the case of the log, all the workers are in recovery state (apache started before tomcat, and someone hit the page so the tomcats are all down). In the log file the requests 5356:1146444096 /Windchill/servlet/WindchillAuthGW/wt.httpgw.HTTPAuthentication/login and 5357:1138932032 /Windchill/servlet/WindchillGW/wt.httpgw.HTTPServer/ping come in almost simultaneously. 5357:1138932032 completes first and picks up tomcat1, recovers it and uses it. However 5356:1146444096 never tries worker 1. 5357:1138932032 grabbed worker 1 before 5356:1146444096 does, and by the time 5356:1146444096 gets the worker list, it never bothers to try tomcat1, just tries all the other workers. As I said, I'm still digging at the mod_jk code to try to find out what's going on, but hoping that maybe someone else has also seen this problem. I can't reproduce this on my system unfortunately, and it's quite intermittent. Andy --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
