SureStop.java from Paul Hyde seems to be fairly professional and robust. But I wonder how it avoids the deadly pitfalls of Thread.stop()? Answer is in the post on unlock@thread death
 Paul even included a test.
Sometimes we do want to forcibly kill a runaway thread. Look at Pushmail. Also,
* a thread stuck in an infinite loop
* a thread blocked in IO
* a thread trying to acquire a lock
Many useful implementation techniques
– SureStop.java is Based on the simple self-running object. In fact SureStop is an extremely simple implementation of a simple idea, given the power it has. Simplicity is power.
– uses highest thread priority to avoid starvation.
– daemon thread