tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yogesh Patel <>
Subject Regarding StuckThreadDetectionValve
Date Mon, 05 Oct 2015 06:54:49 GMT
        We are facing issues with long running thread in tomcat . we are
using Tomcat-7.0.47.Tomcat manager shows Current busy threads : 200,
application  gets stucked due to these long running threads.
         We implemented StuckThreadDetectionValve in server.xml( <Valve


    threshold="60" />), but it  could not help out.
       So we implemented custom StuckThreadDetectionValve by extending
StuckThreadDetectionValve from
catalina, it only goes to "constructor","initInternal",and in "invoke"(when
action fires), it does not go to function "getStuckThreadNames()" even
after threshold time.How to achieve the same.Is there any way to detect
stucked thread and kill them?

  My custom Valve is like following :

public class StuckThreadDetection extends StuckThreadDetectionValve
StuckThreadDetection stuckThreadDetection;

public StuckThreadDetection()
System.out.println("in StuckThreadDetection constructor");


public void invoke(Request request, Response response) throws IOException,
System.out.println("in invoke...");

getNext().invoke(request, response);

protected void initInternal() throws LifecycleException
System.out.println("In initInternal");

public String[] getStuckThreadNames()
System.out.println("in getStuckThreadNames...");
String[] listStuckedThread = this.getStuckThreadNames();

for (String threadName : listStuckedThread)

return listStuckedThread;


public String getInfo()
System.out.println("In getInfo");
return super.getInfo();

*Thanks & Regards,*

* Yogesh Patel*

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message