Mark, I did take 3 thread dumps, but it was after the issue occurred. The thread dumps just show threads in a waiting for work state. They are not doing anything. They are not blocked. When I attach JProfiler to the JVM then it points out that the threads were blocked during that short period of time due to a database connectivity issue. Then Tomcat stops servicing requests. The JVM is up though and has a valid process ID. I would have thought the threads would be in a blocked state for a long period of time in this situation.
Regards, William Crowell ________________________________ From: Mark Thomas <ma...@apache.org> Sent: Tuesday, March 25, 2025 5:09:20 AM To: users@tomcat.apache.org <users@tomcat.apache.org> Subject: Re: NIO Thread Madness On 24/03/2025 18:56, William Crowell wrote: <snip/> > Are there any logs I can enable to find out why the application server stops > accepting connections? I'd suggest taking 3 thread dumps approx 5s apart when this happens. Hopefully you'll see a bunch of threads waiting on the database and where they are waiting will (hopefully) tell you why they are waiting and point you towards a solution. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org CAUTION: This email originated from outside of the organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe. This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.
