https://issues.apache.org/bugzilla/show_bug.cgi?id=47714
--- Comment #3 from Kevin J Walters <k...@ms.com> 2009-11-26 07:03:34 UTC --- 1.2.21 can exhibit request/response mixing - could be the same issue? One way this can occur is some event that triggers a bug where the http response from tomcat ends up buffered. The next request to that apache worker process will then pick up the previous response from the persistent tcp connection. For this particular type of bug, evidence of an ongoing issue can be seen in a few ways: 1) buffered tcp data between tomcat and apache that stays at the same level - easiest to observe when load is very light - run netstat -a a few times and look for established tcp connections with non 0 data in queues. 2) the responses will be way too fast because they are instant due to previous response already waiting 3) if your using prefork and logging worker process pids, you can look for the pattern by comparing things like response size in logs for URLs served by each pid 4) quiesce the server and then fire a series of requests for a known servlet and verify responses match expected result A workaround or preventative measure is DisableReuse -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
