Re: jk-to-tomcat multiple retries

2009-05-06 Thread Rainer Jung
Thanks for letting us know. On 06.05.2009 19:32, Dmitry Beransky wrote: > 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 ;-)

Re: jk-to-tomcat multiple retries

2009-05-06 Thread Dmitry Beransky
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 weir

RE: jk-to-tomcat multiple retries

2009-05-03 Thread Caldarale, Charles R
> From: Dmitry Beransky [mailto:dmitry.ma...@gmail.com] > Subject: Re: jk-to-tomcat multiple retries > > 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 bee

Re: jk-to-tomcat multiple retries

2009-05-02 Thread Rainer Jung
On 01.05.2009 18:19, Dmitry Beransky wrote: > We have the strangest problem started happening to us a few weeks ago > (after several years of running pretty much the same configuration). > > 1. The problem is only happening in the production environment. We > cannot reproduce it on staging, which

Re: jk-to-tomcat multiple retries

2009-05-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dmitry, On 5/1/2009 4:18 PM, Dmitry Beransky wrote: > Hence, I'm asking here for help > diagnosing the problem, but if everyone else is as stumped as I am > then, sure, the next (reluctant) step would be to upgrade Tomcat in > hope that it will go awa

Re: jk-to-tomcat multiple retries

2009-05-01 Thread Dmitry Beransky
> 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? True, but the problem is that I don't have enough data to make a decision. For all I know, there might be something really bad in our code that's triggering

Re: jk-to-tomcat multiple retries

2009-05-01 Thread Christopher Schultz
-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 o

Re: jk-to-tomcat multiple retries

2009-05-01 Thread Dmitry Beransky
> 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. --

Re: jk-to-tomcat multiple retries

2009-05-01 Thread Pid
Dmitry Beransky wrote: > Hi, > > We have the strangest problem started happening to us a few weeks ago > (after several years of running pretty much the same configuration). > > 1. The problem is only happening in the production environment. We > cannot reproduce it on staging, which as far as w

jk-to-tomcat multiple retries

2009-05-01 Thread Dmitry Beransky
Hi, We have the strangest problem started happening to us a few weeks ago (after several years of running pretty much the same configuration). 1. The problem is only happening in the production environment. We cannot reproduce it on staging, which as far as we can tell is configured identically