Radhika

yes.We can rethrow an exception.try { // code here that throws an Exception } catch (Throwable t) { throw t; // (re)throw it in their face } Example: //Rethrowing.java // Demonstrating fillInStackTrace() public class Rethrowing { public static void first() throws Exception { System.out.println("originating the exception in first()"); throw new Exception("thrown from first()"); } public static void getexception() throws Throwable { try { first(); } catch(Exception e) { System.out.println( "Inside getexception (), e.printStackTrace()"); e.printStackTrace(); throw e; // 17 // throw e.fillInStackTrace(); // 18 } } public static void main(String[] args) throws Throwable { try { getexception (); } catch(Exception e) { System.out.println( "Caught in main, e.printStackTrace()"); e.printStackTrace(); } } } ///:~ The important line numbers are marked inside of comments. With line 17 un-commented (as shown), the output is: originating the exception in f() Inside getexception (), e.printStackTrace() java.lang.Exception: thrown from f() at Rethrowing.first(Rethrowing.java:8) at Rethrowing. getexception (Rethrowing.java:12) at Rethrowing.main(Rethrowing.java:24) Caught in main, e.printStackTrace() java.lang.Exception: thrown from f() at Rethrowing.first(Rethrowing.java:8) at Rethrowing. getexception (Rethrowing.java:12) at Rethrowing.main(Rethrowing.java:24) So the exception stack trace always remembers its true point of origin, no matter how many times it gets rethrown. With line 17 commented and line 18 un-commented, fillInStackTrace( ) is used instead, and the result is: originating the exception in f() Inside getexception (), e.printStackTrace() java.lang.Exception: thrown from first() at Rethrowing.first(Rethrowing.java:8) • at Rethrowing. getexception (Rethrowing.java:12) • at Rethrowing.main(Rethrowing.java:24)