Java – why is interruptedexception a checked exception?

When dealing with threads in Java, dealing with interruptedexception seems to be a special thorn around me I appreciate the fact that my thread is thrown when it is terminated, so I have the opportunity to clean it up It seems strange to me that this is not an unchecked exception

This causes the following problems: a) if I want to use an existing framework in my threaded application, I have to convert it to an exception accepted by the framework interface Therefore, frameworks often misunderstand it rather than clean it up or disseminate it according to it

b) Unless interruptedexception is strictly declared for each call in the stack (and usually not because of a), it is difficult to close cleanly

If you uncheck interruptedexception, it seems to have a higher probability and usually leads to clean shutdown of threads and applications Why not?

Solution

Interruption should be cooperative I think designers want to avoid a situation where you can eliminate a thread by interrupting it, and the thread has no code to deal with this possibility The goal seems to be to let runnable code decide exactly how to handle interrupts Many frameworks or language codes seem to be about deciding who should do what, and trying to make the correct usage obvious in order to minimize the extent to which users are burned This is one of the judgments

When checking for interruptedexceptions, the worst case scenario is that the exception is caught, but in a very useful way (in fact, the absolute worst case is that the interrupt flag is not restored, and any subsequent code in the thread is not aware of the interrupt.) If interruptedexception is unchecked (or if you wrap it in a runtimeException, as shown in the linked article) comment), the exception may not be handled and continue to terminate the thread, which may be very bad if the thread is not in the stop position

Use unchecked interruptedexceptions to make better use of toy examples and simple code; No one will bother to catch exceptions and it will work However, doing a lot of work in real code can be considered harmful

The purpose of checking exceptions is to ensure that developers know that exceptions can be thrown, so that developers can avoid throwing exceptions in the ongoing work of the thread, which may make the work partially complete A bad state