2014-06-19 17:10 GMT+04:00 Lars Engholm Johansen <lar...@gmail.com>: > I will try to force a GC next time I am at the console about to restart a > Tomcat where one of the http-nio-80-ClientPoller-x threads have died and > connection count is exploding. > > But I do not see this as a solution - can you somehow deduct why this > thread died from the outcome from a GC?
Nobody said that a thread died because of GC. The GC that Andre suggested was to get rid of some of CLOSE_WAIT connections in netstat output, in case if those are owned by some abandoned and non properly closed I/O classes that are still present in JVM memory. > And could an Exception/Error in Tomcat thread http-nio-80-ClientPoller-0 > or http-nio-80-ClientPoller-1 make the thread die with no Stacktrace in > the Tomcat logs? > A critical error (java.lang.ThreadDeath, java.lang.VirtualMachineError) will cause death of a thread. A subtype of the latter is java.lang.OutOfMemoryError. As of now, such errors are passed through and are not logged by Tomcat, but are logged by java.lang.ThreadGroup.uncaughtException(). ThreadGroup prints them to System.err (catalina.out). Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
