Skip to main content

Killing a particular Tomcat thread

Update: This JSP does not work on a thread that is inside some native code.  On many occasions I had a thread stuck in JNI code and it wont work.
Also in some cases thread.stop can cause jvm to hang. According to javadocs "This method is inherently unsafe. Stopping a thread with Thread.stop causes it to unlock all of the monitors that it has locked".

I have used it only in some rare occasions where I wanted to avoid a system shutdown and in some cases we ended up doing system shutdown as jvm was hung so I had a 70-80% success with it. 
 --------------------------------------------------------------------------------------------------------------------------
We had an interesting requirement. A tomcat thread that was spawned from an ExecutorService ThreadPool had gone Rogue and was causing lots of disk churning issues. We cant bring down the production server as that would involve downtime. Killing this thread was harmless but how to kill it, the ExecutorService variable was private and we can't call shutdownNow on it. So the solution was to generate a ThreadDump get the threaName and write a JSP to kill it. Much of the code is borrowed but as this is a unique issue , I thought of helping fellow Googlers ;).



<%@page language="java"%>
<%
    String threadNameToKill = request.getParameter("threadNameToKill");
    killThread(threadNameToKill, out);
%>
<%!
    public void killThread(String threadNameToKill, JspWriter out) throws Exception {
        ThreadGroup root = Thread.currentThread().getThreadGroup().getParent();
        while (root.getParent() != null) {
            root = root.getParent();
        }
        visit(root, 0, threadNameToKill,out);
    }

    public void visit(ThreadGroup group, int level, String threadNameToKill,JspWriter out) throws Exception {
        int numThreads = group.activeCount();
        Thread[] threads = new Thread[numThreads * 2];
        numThreads = group.enumerate(threads, false);
        for (int i = 0; i < numThreads; i++) { // Get thread
            Thread thread = threads[i];
            if (threadNameToKill.equals(thread.getName())) {
                thread.stop();
                out.write("Thread " + threadNameToKill + "Killed");
                break;
            }
        }
        int numGroups = group.activeGroupCount();
        ThreadGroup[] groups = new ThreadGroup[numGroups * 2];
        numGroups = group.enumerate(groups, false);
        for (int i = 0; i < numGroups; i++) {
            visit(groups[i], level + 1, threadNameToKill, out);
        }
    }
%>

Comments

  1. Nice hack ... in reading this, my first instinct was that there ought to be a standard JMX Operation for doing this. But I fired up jconsole & it looks like there is no such thing, so your approach looks to be the only option.

    I guess if this happens on a server where you don't have some kind of dynamic classloading/scripting you're out of luck!

    ReplyDelete
  2. Yes for the same reason JSPs are a blessing for us and I don't have telnet access to production machines so things like ThreadDump and SystemStats JSPs are heaven. I still haven't enabled JMX here as its a pain to enable them for Tomcat and there are tons of other interesting things to do. Will do JMX as thats a proper way when get some breathing room.

    ReplyDelete
  3. This function looks like good, but actually it seems not work, when I kill a thread, I tomcat won't re-create a new thread, and the whole tomcat system hangs after a while, no request can be processed any more.

    ReplyDelete
  4. You are right. Please check my update at top.

    ReplyDelete

Post a Comment

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

What a rocky start to labor day weekend

Woke up by earthquake at 7:00 AM in morning and then couldn't get to sleep. I took a bath, made my tea and started checking emails and saw that after last night deployment three storage node out of 100s of nodes were running into Full GC. What was special about the 3 nodes was that each one was in a different Data centre but it was named same app02.  This got me curious I asked the node to be taken out of rotation and take a heap dump.  Yesterday night a new release has happened and I had upgraded spymemcached library version as new relic now natively supports instrumentation on it so it was a suspect. And the hunch was a bullseye, the heap dump clearly showed it taking 1.3G and full GCs were taking 6 sec but not claiming anything.



I have a quartz job in each jvm that takes a thread dump every 5 minutes and saves last 300 of them, checking few of them quickly showed a common thread among all 3 data centres. It seems there was a long running job that was trying to replicate pending…