Course contentsShow
← Java
Lesson 732 of 2,87018. Exception Handling FundamentalsFree lesson

Accessing Exception Information in catch Blocks

Explore how to use the caught exception object to retrieve error messages, stack traces, and causes.

Accessing Exception Information in catch Blocks

What you'll learn: How to extract useful information from caught exception objects to understand what went wrong.

The Exception Object as Your Error Detective

When you catch an exception, Java gives you an exception object—a variable that holds all the details about what went wrong. This object isn't just a placeholder; it's packed with information like error messages, the sequence of method calls that led to the problem, and even the root cause if one exception triggered another.

Think of the exception object like a flight recorder from an airplane: when something crashes, you can examine it to understand exactly what happened, when, and where.

Core Exception Methods

The exception object provides several key methods:

try {
    int result = 10 / 0;  // ArithmeticException
} catch (ArithmeticException e) {
    String message = e.getMessage();
    System.out.println("Error: " + message);  // "/ by zero"
    
    String details = e.toString();
    System.out.println(details);  // "java.lang.ArithmeticException: / by zero"
    
    e.printStackTrace();  // Prints full stack trace to console
}
  • getMessage(): Returns a short description of the error
  • toString(): Returns the exception class name plus the message
  • printStackTrace(): Displays the complete chain of method calls that led to the exception

When to Use Each

Use getMessage() when you want to display user-friendly error information. Use printStackTrace() during development and debugging to see exactly where things went wrong. The stack trace shows you the file names, line numbers, and method call sequence—invaluable for troubleshooting.

Key Takeaway: The caught exception object is your primary tool for diagnosing errors; use getMessage() for simple descriptions, toString() for formatted output, and printStackTrace() for detailed debugging information.