Exception Handling
Exception Handling
An exception is a problem that arises during the execution of a program. An exception can occur for many
different reasons, including the following:
A user has entered invalid data.
A file that needs to be opened cannot be found.
A network connection has been lost in the middle of communications or the JVM has run out of memory.
Some of these exceptions are caused by user error, others by programmer error, and others by physical
resources that have failed in some manner.
To understand how exception handling works in Java, you need to understand the three categories of
exceptions:
Checked exceptions:
A checked exception is an exception that is typically a user error or a problem that cannot be foreseen by the
programmer. For example, if a file is to be opened, but the file cannot be found, an exception occurs. These
exceptions cannot simply be ignored at the time of compilation.
Runtime exceptions: A runtime exception is an exception that occurs that probably could have been avoided by the
programmer. As opposed to checked exceptions, runtime exceptions are ignored at the time of compilation.
Errors: These are not exceptions at all, but problems that arise beyond the control of the user or the programmer. Errors
are typically ignored in your code because you can rarely do anything about an error. For example, if a stack overflow
occurs, an error will arise. They are also ignored at the time of compilation.
Exception Hierarchy:
All exception classes are subtypes of the java.lang.Exception class. The exception class is a subclass of the Throwable class.
Other than the exception class there is another subclass called Error which is derived from the Throwable class.
Errors are not normally trapped form the Java programs. These conditions normally happen in case of severe failures, which
are not handled by the java programs. Errors are generated to indicate errors generated by the runtime environment.
Example : JVM is out of Memory. Normally programs cannot recover from errors.
The Exception class has two main subclasses: IOException class and Runtime Exception Class.
Here is a list of most common checked and unchecked Java's Built-in Exceptions.
Exceptions Methods:
Following is the list of important methods available in the Throwable class.
Methods with Description
1. public String getMessage():
Returns a detailed message about the exception that has occurred. This message is initialized in the
Throwable constructor.
2. public Throwable getCause():
Returns the cause of the exception as represented by a Throwable object.
3. public String toString():
Returns the name of the class concatenated with the result of getMessage()
4. public void printStackTrace():
Prints the result of toString() along with the stack trace to System.err, the error output stream.
5. public StackTraceElement [] getStackTrace():
Returns an array containing each element on the stack trace. The element at index 0 represents the top of the
call stack, and the last element in the array represents the method at the bottom of the call stack.
6. public Throwable fillInStackTrace():
Fills the stack trace of this Throwable object with the current stack trace, adding to any previous information
in the stack trace.
Catching Exceptions:
A method catches an exception using a combination of the try and catch keywords. A try/catch block is placed around the
code that might generate an exception. Code within a try/catch block is referred to as protected code, and the syntax for
using try/catch looks like the following:
try
{
//Protected code
}catch(ExceptionName e1)
{
//Catch block
}
A catch statement involves declaring the type of exception you are trying to catch. If an exception occurs in protected code,
the catch block (or blocks) that follows the try is checked. If the type of exception that occurred is listed in a catch block,
the exception is passed to the catch block much as an argument is passed into a method parameter.
Example:
The following is an array is declared with 2 elements. Then the code tries to access the 3rd element of the array which
throws an exception.
// File Name : ExcepTest.java
import java.io.*;
publicclassExcepTest{
import java.io.*;
publicclass className
{
publicvoid deposit(double amount)throwsRemoteException
{
// Method implementation
thrownewRemoteException();
}
//Remainder of class definition
}
A method can declare that it throws more than one exception, in which case the exceptions are declared in a list separated
by commas. For example, the following method declares that it throws a RemoteException and an
InsufficientFundsException:
import java.io.*;
publicclass className
{
publicvoid withdraw(double amount)throwsRemoteException,
InsufficientFundsException
{
// Method implementation
}
//Remainder of class definition
}
The finally Keyword
The finally keyword is used to create a block of code that follows a try block. A finally block of code always executes,
whether or not an exception has occurred.
Using a finally block allows you to run any cleanup-type statements that you want to execute, no matter what happens in the
protected code.
A finally block appears at the end of the catch blocks and has the following syntax:
try
{
//Protected code
}catch(ExceptionType1 e1)
{
//Catch block
}catch(ExceptionType2 e2)
{
//Catch block
}catch(ExceptionType3 e3)
{
//Catch block
}finally
{
//The finally block always executes.
}
Example:
publicclassExcepTest{
publicstaticvoid main(String args[]){
int a[]=newint[2];
try{
System.out.println("Access element three :"+ a[3]);
}catch(ArrayIndexOutOfBoundsException e){
System.out.println("Exception thrown :"+ e);
}
finally{
a[0]=6;
System.out.println("First element value: "+a[0]);
System.out.println("The finally statement is executed");
}
}
}