interrupt() is not a static method. One thread sends an interrupt to another thread t by calling t.interrupt(). t.interrupt() has the following effect:- 1. if t is running then the only effect is set an interrupted flag in t. If after the interrupted flag is set, there is an attempt to make t go into waiting by calling sleep() or wait(), then it immediately throws InterruptedException. 2. if t is waiting when interrupt is received, then it throws InterruptedException, and awakens. interrupt is normally sent for stopping/suspending threads. Note that interrupt by itself does NOT stop/suspend thread. Rather it used for this purpose. To understand how it may be used to stop threads see Peter Hagar's post in http://www.javaranch.com/ubb/Forum27/HTML/000247.html Since stop() and suspend() are deprecated, the above idiom is the recommended way of stopping/suspending threads. There are a lot of old posts explaining the role of interrupt. I myself learnt a lot from Maha Anna's post.
I removed the pointless "URGENT" from the title. CLG, most of the behavior above is described in the Thread API, isn't it? Not just under interrupt() - there are various references to "interrupt status" and "interrupted status" throughout the class. Some details are covered under wait() or sleep() instead. What particular part or parts above are you questioning?