One consequence of using a RemotingException subclass is that, unlike when using InterruptedException, the thread must be re-interrupted before throwing the exception. So user code that doesn't check for it, will be interrupted at the next interruptable point anyway. On the other hand, if the user does catch the interruption subclass, they may have to clear the thread's interruption status in addition to catching the exception. This is in contrast to user code that catches InterruptedException; such code already has had the thread's interruption status cleared. I'm not sure if this will be an advantage or disadvantage though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085816#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...