tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 50306] Detect stuck threads
Date Mon, 22 Nov 2010 19:22:10 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=50306

--- Comment #6 from Sylvain Laurent <sylvain.laurent@gmail.com> 2010-11-22 14:22:05
EST ---
My initial idea was : if a request takes too long, log a WARNING with the stack
trace of the thread processing the request.
I think that it is important to have this in log file (push information) than
to just allow access by JMX (pull information) because it allows to discover
problems pro-actively, for instance a network call that is stuck waiting for
data from an unhealthy server and no socket timeout has been set for the call.

As for the actual implementation, it could indeed be a LifeCycleListener, but
it will probably need some changes elsewhere to provide instrumentation.

I'll try to propose a patch in a couple of days.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message