Michael,
On 1/18/25 2:22 AM, Michael wrote:
Hi Chris,
Yes, there's only the HTTP connector on port 8080. There's a load
balancer in front of this that handles HTTPS.
If you connect the client directly to Tomcat, are you still able to
reproduce the errors?
I have only seen the NPE thrown from CoyoteOutputStream.flush() in
production environments that use a load balancer.
But when connecting directly to Tomcat in my devel environment, I was
able to reproduce the behavior with the exception causing errors in
requests handled by another application.
Try adding this to your <Connector> configuration in development and
pounding on it again:
discardFacades="true"
This ought to be the default, but ... just in case.
Are you able to reduce the test case to something you could share with
the Tomcat dev team? I know that's a big ask, but the other option is to
enable tons of logging and have what is likely to be a very long and
draw-out conversation with you via email.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
