Izek,
On 10/22/24 15:05, Izek Hornbeck wrote:
Right now we are only using HTTP/1.1--do you think that could make a
difference?
Only in that is reduces the number of places in Tomcat where a 400
response is sent.
I would say it is reproducible... as far as I can recall, I see this at
least
Thanks for following up, Chris!
Right now we are only using HTTP/1.1--do you think that could make a
difference?
I would say it is reproducible... as far as I can recall, I see this at
least the first time in a day that I access each application deployed on
tomcat, and some other times during the
Izek,
On 10/16/24 18:07, Izek Hornbeck wrote:
I have confirmed that our development team has seen these same loading
issues with Tomcat 9.0.55 and 9.0.86.
Are you using HTTP/2 or AJP at all? Or only HTTP/1.1?
Is it at all reprodicible or are you just looking at log files?
It's definitely pos
I have confirmed that our development team has seen these same loading
issues with Tomcat 9.0.55 and 9.0.86.
On Wed, Oct 16, 2024 at 3:22 PM Izek Hornbeck
wrote:
> We are working on a large upgrade for this application, so we are looking
> at upgrading Tomcat too (either to version 10 if we can
We are working on a large upgrade for this application, so we are looking
at upgrading Tomcat too (either to version 10 if we can resolve the
javax/jakarta issues or just to the current 9.0.x). I'll try some tests
locally to see what impact newer versions could have.
In the access logs, we occasio
> On Oct 11, 2024, at 12:48, Izek Hornbeck wrote:
>
> My team has a Java web app (java v17.0.2) running on a Tomcat 9.0.40
> server.
Which is almost 4 years old. You really, really need to catch up.
> When we upgraded to Tomcat 9, we found that occasionally, some css
> files and images woul
