-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dmitry,
On 5/1/2009 12:37 PM, Dmitry Beransky wrote: >> Upgrade that Tomcat, it is *years* old - 5.5.27 is the latest. >> See if it still does it then. > > Unfortunately, the pesky reality is that I would not be permitted to > do such an upgrade to our entire infrastructure until I can show that > all other options have been exhausted. If you suspect a bug in Tomcat, wouldn't upgrading to a version of Tomcat where that bug had potentially been fixed be a good strategy? It's really too bad you can't reproduce the error in your staging environment. Is there a way for you to re-play activity from your production logs against a staging server to generate the proper load and/or usage profile? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkn7NzEACgkQ9CaO5/Lv0PCOXgCgrdYdI24T5mcNzqaWKOEQp5Sp NYgAoIu62TY/6VtrNZJBaNoHC+/3BkMm =Ioh3 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
