Handling Errors using Exceptions

Putting It All Together

When all of the components are put togehter, the writeList() method will look like this:

public void writeList() {
    PrintStream pStr = null;

    try {
        int i;

        System.err.println("Entering try statement");
        pStr = new PrintStream(
              new BufferedOutputStream(
                 new FileOutputStream("OutFile.txt")));

        for (i = 0; i < size; i++)
            pStr.println("Value at: " + i + " = " + victor.elementAt(i));
    } catch (ArrayIndexOutOfBoundsException e) {
        System.err.println("Caught ArrayIndexOutOfBoundsException: " + e.getMessage());
    } catch (IOException e) {
        System.err.println("Caught IOException: " + e.getMessage());
    } finally {
        if (pStr != null) {
            System.err.println("Closing PrintStream");
            pStr.close();
        } else {
            System.err.println("PrintStream not open");
        }
    }
}  

This try block in this method has three different exit possibilities:

1. The new FileOutputStream statement fails and throws an IOException.
2. The victor.elementAt(i) statement fails and throws an ArrayIndexOutOfBoundsException.
3. Everything succeeds and the try statement exits normally.

This page investigates in detail what happens in the writeList() method during each of those exit possibilities.

Scenario 1: An IOException Occurs

The new FileOutputStream("OutFile.txt") statement can fail for any number of reasons: the user doesn't have write permission on the file or directory, the file system is full, or the directory for the file doesn't exist. If any of these situations is true, then the constructor for FileOutputStream throws an IOException.

When the IOException is thrown, the runtime system immediately stops execution of the try block. Then the runtime system attempts to locate an exception handler appropriate for handling an IOException.

The runtime system immediately takes over and tries to locate an appropriate exception handler. The runtime system begins its search at the top of the method call stack. When the exception occurred, the FileOutputStream constructor was at the top of the call stack. However, the FileOutputStream constructor doesn't have an appropriate exception handler so the runtime system checks the next method in the method call stack--the writeList() method. The writeList() method has two exception handlers: one for ArrayIndexOutOfBoundsException and one for IOException.

The runtime system checks writeList's handlers in the order that they appear following the try statement. The argument to the first exception handler is ArrayIndexOutOfBoundsException, but the exception that was thrown is an IOException. An IOException cannot legally be assigned to an ArrayIndexOutOfBoundsException, so the runtime system continues its search for an appropriate exception handler.

The argument to writeList()'s second exception handler is an IOException. The exception thrown by the FileOutputStream constructor is also an IOException and can be legally assigned to the handler's IOException argument. Thus, this handler is deemed appropriate and the runtime system executes this handler which prints this statement:

Caught IOException: OutFile.txt

After the exception handler has run, the runtime system passes control to the finally block. In this particular scenario, the PrintStream never got opened, thus pStr is null and won't get closed. After the finally block has completed executing, the program continues with the first statement after the finally block.

The complete output that you will see from the ListOfNumbers program when an IOException is thrown is this:

Entering try statement
Caught IOException: OutFile.txt
PrintStream not open

Scenario 2: An ArrayIndexOutOfBoundsException Occurs

This scenario is the same as the first except that a different error occurs during the try block. In this scenario, the argument passed to Vector's elementAt() method is out of bounds. That is, the argument is either less than 0 or is larger than the size of the array. (The way the code is written, this is actually impossible, but let's suppose a bug is introduced into the code when someone modifies it.)

Similar to scenario 1, when the exception occurs the runtime system stops execution of the try block and attempts to locate an exception handler suitable for an ArrayIndexOutOfBoundsException. The runtime system searches for an appropriate exception handler as it did before and comes upon the catch statement in the writeList() method that handles exceptions of the type ArrayIndexOutOfBoundsException and executes it.

After the exception handler has run, the runtime system passes control to the finally block. In this particular scenario, the PrintStream did get opened, thus the finally statement closes it. After the finally block has completed executing, the program continues with the first statement after the finally block.

The complete output that you will see from the ListOfNumbers program when an ArrayIndexOutOfBoundsException is thrown is this:

Entering try statement
Caught ArrayIndexOutOfBoundsException: 10 >= 10
Closing PrintStream

Scenario 3: The try block exits normally

In this scenario, all the statements within the scope of the try block execute successfully and throw no exceptions. Execution falls off the end of the try block and then the runtime system passes control to the finally block. Since everything was successful, we know that the PrintStream is open when control reaches the finally block and must be closed. Again, after the finally block has completed executing, the program continues with the first statement after the finally block.

Thus, the output that you will see from the ListOfNumbers program when no exceptions are thrown is:

Entering try statement
Closing PrintStream

Handling Errors using Exceptions