> It was pointed out to me by a colleague that we're not properly> handling InterruptedException in many places.>> He cited this article (I could only find it in Chinese, but Google> Translate works quite well converting it to English):> http://www.ibm.com/developerworks/cn/java/j-jtp05236.html>> One place we do this a lot is UtilWaitThread. Should we be concerned> about this? How do we want to address it?>> (Also, does anybody have a link to the English version of that article?)>> --> Christopher L Tubbs II> http://gravatar.com/ctubbsii>

That's a great article! Brian Goetz's book Java Concurrency in Practice hasmaterial like this and *tons* more. That book along with Effective Java byBloch oughta be on every Java developer's bookshelf. :)

UtilWaitThread looks to me like it exists just to provide a sleep that eatsInterruptedException so you don't have to deal with it, which is prettymuch a bad idea. It prevents threads who use it from properly dying outwhen receiving an interrupt. Eventually the method should be eliminated sothat threads can correctly propagate interrupts as the article describes.