This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I wanted to see what would happen when an object is blocked and inetrrupt method is called on the thread. I made this program. Now I don't understand why it's behaving the way its behaving. On my PC it simply hangs there for a while and after a few seconds gives an error. Is this program doing the same acts on your computer. Can anyone tell me whats happening and how to tame it. It would be great if I also can get a program that causes a runtime error to occur because interrupt was called and the thread was blocked. But the should be because the thread was blocked and only blocked not waiting and not sleeping. One more thing can I call thread.setPriority() after the call to thread.start(). well here goes my wild code :
If the interrupt method is invoked on a thread that is sleeping or waiting then an InterruptedException is thrown. If the thread is not in the not-runnable state, then the thread won't know that it has been interrupted unless it checks the isInterrupted method.
Dan Chisholm<br />SCJP 1.4<br /> <br /><a href="http://www.danchisholm.net/" target="_blank" rel="nofollow">Try my mock exam.</a>