I’m just trying to understand, is there really a plausible solution here ? Unless we have loadbalanced tomcat instances, can we truly ever stop such behaviour (or more importantly, does it make sense to do so)?
For my use case, We do it in production almost every other day for patching, but we do it on our 60 servers over a duration of 15-20 minutes (and by rolling 1-by-1). That said, this may not be an acceptable delay/solution for others. Also, if it happens to be a critical piece (index.jsp or something more client-faces), you may not be able to wait that long. It’s be good to know what others think. Regards, On Mon, 4 Nov 2019 at 22:55, Alex O'Ree <alexo...@apache.org> wrote: > Sounds a lot like the issue I reported a few months ago.... > > On Mon, Nov 4, 2019, 3:12 PM Tim K <tim.k.5...@gmail.com> wrote: > > > On Mon, Nov 4, 2019, 10:30 AM Mark Thomas <ma...@apache.org> wrote: > > > > > > > > Thanks. That helps as it means the issue should be reproducible on a > > > single, stand-alone instance. > > > > > > Mark > > > > > > > I was able to reproduce this behavior with a single server running a > > vanilla 9.0.21 using the example hello.jsp file... I was hitting the url > > every 0.5 seconds. > > > > > > > >
