Java does not go through catch (Exception e) directly to finally or exit reason

Today has a very wonderful problem! At the time of writing the Hadoop program! New An Object! The program runs directly to the finally code block! The exception in the catch also did not execute.

New Configuration ();

I wonder for a long time! I went to see the source of Hadoop! The new object is not doing anything, just some normal assignment! Later on the internet to find a long time to find that the original was turned into a throwable thrown! And exception is Throwable sub-class, so can not capture, only the time to capture Throwable, the error message to print!

This is due to the fact that there is a static variable in the configuration class of Hadoop and an exception occurred when ClassLoader loaded class.

Private Static Final Log log =    logfactory.getlog (Configuration. class);

My mistake was retarded, just because I didn't add the common-logging bag! Believe the general situation this kind of thing very few people will encounter! But today, it is a lesson to be learned, so that people with this kind of doubt can be solved! So, don't think catch (Exception e) is all right, Throwable is the ultimate boss!

And why is it that Throwable is thrown here instead of exception? I've never found a reason to find it! I hope that Daniel can tell you! My little brother thanked me here!

　　

Java does not go through catch (Exception e) directly to finally or exit reason