On Thu, Jan 23, 2025 at 5:30 PM Mark Thomas <ma...@apache.org> wrote: > > In the case of the unit test, it was a client disconnect during async > processing that triggered the issue.
That sounds a lot like the situation we have seen. > It would be worth testing with a 10.1.x build if you can. You can either > build Tomcat from source or get a snapshot build from the CI system in a > couple of hours once it has build the latest 10.1.x > > If this Tomcat bug was the cause of all the issues then great. That > said, it is usually the case that more than one thing is going wrong. > Fixing one thing just makes the next one easier to see. Do let us know > how you get on once the NPE issue is out of the picture. Thanks a lot for the fix! As far as I can tell, it is somehow equivalent to the way I've handle the NPE in the application code (we now catch the NPE and handle it as we handle IOExceptions), so I'm quite confident that it will also solve the problem we've seen. I think there may be something with our implementation of part of the AsyncListener interface when for instance the onError timing is bad for us (which was also noted earlier in this thread). I'll try to get some time to look into that, but as we don't see the problem anymore, I've had some more urgent this to work on and it might take a while. Thanks for all your comments and work on this issue to everyone that took the time to write in this thread! /Michael --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
