-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yuval,
On 2/11/2009 1:56 AM, Yuval Perlov wrote: > What leads me to believe this is unrelated to my application code is > that restarting apache makes the problem go away. So, when your site goes crazy, a simple httpd-bounce does the trick? No Tomcat restart or anything required? Existing users and sessions are all preserved and pretty much the problem just magically goes away? Crazy. I see that you are using httpd 2.2.10. Have you tried downgrading to 2.0.x to see if that helps? I've heard some folks having trouble with mod_jk 1.2.27, so you might try downgrading to 1.2.26 unless something vital is in the .27 release that you need. Those are easier fixes than switching to proxy_http or removing httpd altogether. If you watch the network traffic with a TCP sniffer like wireshark, does it look like request A results in response B instead of (expected) response A? When the server goes crazy, can you start sending TRACE requests to see if those get mixed-up? Does all traffic get jumbled, or just the stuff bound for Tomcat? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmS1lgACgkQ9CaO5/Lv0PBNTwCghqlzDnFDppy0WmgHGTdKjMoQ czQAnijlks4T6XAM72WuC3EgMN1NB+0Q =xzLb -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
