wood burning stoves*
The moose likes Programmer Certification (SCJP/OCPJP) and the fly likes Q on Exception Handling Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Certification » Programmer Certification (SCJP/OCPJP)
Bookmark "Q on Exception Handling" Watch "Q on Exception Handling" New topic

Q on Exception Handling

priti manas duddilla

Joined: Jul 17, 2007
Posts: 25

What is the result?
A. test end
B. Compilation fails.
C. test runtime end
D. test exception end
E. A Throwable is thrown by main at runtime.
Answer: D

Why doestn't the Catch block in Main() execute?
and how come System.out.print(�end �); executed?
Ranch Hand

Joined: Nov 22, 2008
Posts: 18944
Hi Priti Manas,

The exception which is thrown on line 14, is a RuntimeException which extends Exception. This exception is caught at line 16 and handled. Once handled we are safe from exception. So the exception is not thrown out of test method and need not be handled at line 20. In fact exception does not come out of test method at all, and since we have proper precautions at line 20 , we are good to execute line 21.

Assume, the exception thrown at line 14 is not caught within method test() and is thrown back to main method, and even there it is not properly handled then line 21 throws compiler error, saying "Unreachable code".
Doug Slattery
Ranch Hand

Joined: Sep 15, 2007
Posts: 294
Originally posted by priti manas duddilla:
Why doestn't the Catch block in Main() execute?
and how come System.out.print(�end �); executed?

Hi Priti,

The main() catch block doesn't execute because the exception is not re-thrown from the test() method. The catch() block in the test() method catches the exception thrown by the test() method. If you want the method that calls test() to react to exceptions, you need to throw it again. You can do this in a few different ways.

1: you can add a line inside the catch block at line 16 to throw the exception again. (Add it after the System.out.print() line.)

2: you can add a finally block after line 16 with a throw in it. In this case, the finally() block will be called from the catch() block at 16, *NOT* the try() block at 12.

3: you can add a throw outside of the try/catch block between lines 16 and 17. Execution of the method doesn't stop with the catch() block unless you return or exit within it.

Hope this helps...
priti manas duddilla

Joined: Jul 17, 2007
Posts: 25
Oh thats nice explanation over there!

But is it the case with checked exceptions too?
I think they propagate no matter what, even after being handled right?

Please clarify.
Peter Mularien
Ranch Hand

Joined: Sep 06, 2007
Posts: 84
No - once a Throwable (of which Exception is a subclass) is caught by a catch block, it will *never* propagate unless it is explicitly rethrown from the catch block.

Author, Spring Security 3 (the Book), Packt Publishing, 2010
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
subject: Q on Exception Handling
Similar Threads
Question from mock site
Doubt in Error/AssertionError
Question on assertion error
Exception output