Java Exception Handling Interview Questions and Answers

What is Exception in Java?

1. An exception is an error event that can happen during the execution of a program and disrupts its normal flow. An exception can arise from different kind of situations such as wrong data entered by the user, hardware failure, network connection failure, etc.
   Whenever any error occurs while executing a java statement, an exception object is created and then JRE tries to find an exception handler to handle the exception. If suitable exception handler is found then the exception object is passed to the handler code to process the exception, known as catching the exception. If no handler is found then application throws the exception to the runtime environment and JRE terminates the program.
   Java Exception handling framework is used to handle runtime errors only, compile-time errors are not handled by the exception handling framework.

Java exception handling interview questions

What is the Exception Handling Keywords in Java?

1. There are four keywords used in java exception handling.
   1. throw: Sometimes we explicitly want to create an exception object and then throw it to halt the normal processing of the program. The throws keyword is used to throw an exception to the runtime to handle it.
   2. throws: When we are throwing any checked exception in a method and not handling it, then we need to use throws keyword in method signature to let caller program know the exceptions that might be thrown by the method. The caller method might handle these exceptions or propagate it to its caller method using keyword. We can provide multiple exceptions in the throws clause and it can be used with main() method also.
   3. try-catch: We use try-catch block for exception handling in our code. try is the start of the block and catch is at the end of try block to handle the exceptions. We can have multiple catch blocks with a try and try-catch block can be nested also. catch block requires a parameter that should be of type Exception.
   4. finally: finally block is optional and can be used only with try-catch block. Since exception halts the process of execution, we might have some resources open that will not get closed, so we can use finally block. finally, the block gets executed always, whether an exception occurred or not.

Explain Java Exception Hierarchy?

1. Java Exceptions are hierarchical and inheritance is used to categorize different types of exceptions. Throwable is the parent class of Java Exceptions Hierarchy and it has two child objects – Error and Exception. Exceptions are further divided into checked exceptions and runtime exception.
   Errors are exceptional scenarios that are out of the scope of application and it’s not possible to anticipate and recover from them, for example, hardware failure, JVM crash or out of memory error.
   Checked Exceptions are exceptional scenarios that we can anticipate in a program and try to recover from it, for example, FileNotFoundException. We should catch this exception and provide a useful message to the user and log it properly for debugging purpose. Exception is the parent class of all Checked Exceptions.
   Runtime Exceptions are caused by bad programming, for example, trying to retrieve an element from the Array. We should check the length of array first before trying to retrieve the element otherwise it might throw ArrayIndexOutOfBoundException at runtime. RuntimeException is the parent class of all runtime exceptions.

Java exception handling interview questions

What are important methods of Java Exception Class?

1. Exception and all of its subclasses don’t provide any specific methods and all of the methods are defined in the base class Throwable.
   1. String getMessage() – This method returns the message String of Throwable and the message can be provided while creating the exception though it’s a constructor.
   2. String getLocalizedMessage() – This method is provided so that subclasses can override it to provide the locale-specific message to the calling program. Throwable class implementation of this method simply uses the method to return the exception message.
   3. synchronized Throwable getCause() – This method returns the cause of the exception or null if the cause is unknown.
   4. String toString() – This method returns the information about Throwable in String format, the returned String contains the name of Throwable class and localized message.
   5. void printStackTrace() – This method prints the stack trace information to the standard error stream, this method is overloaded and we can pass PrintStream or PrintWriter as the argument to write the stack trace information to the file or stream.

Explain Java 7 ARM Feature and multi-catch block?

1. If you are catching a lot of exceptions in a single try block, you will notice that catch block code looks very ugly and mostly consists of redundant code to log the error, keeping this in mind Java 7 one of the features was the multi-catch block where we can catch multiple exceptions in a single catch block. The catch block with this feature looks like below:

   
   catch(IOException | SQLException | Exception ex){
        logger.error(ex);
        throw new MyException(ex.getMessage());
   }
   

   Most of the time, we use finally block just to close the resources and sometimes we forget to close them and get runtime exceptions when the resources are exhausted. These exceptions are hard to debug and we might need to look into each place where we are using that type of resource to make sure we are closing it. So Java 7 one of the improvement was try-with-resources where we can create a resource in the try statement itself and use it inside the try-catch block. When the execution comes out of the try-catch block, runtime environment automatically closes these resources. Sample of the try-catch block with this improvement is:

   
   try (MyResource mr = new MyResource()) {
               System.out.println("MyResource created in try-with-resources");
           } catch (Exception e) {
               e.printStackTrace();
           }
   

   
   

Java exception handling interview questions

What is the difference between Checked and Unchecked Exception in Java?

1. 1. Checked Exceptions should be handled in the code using try-catch block or else method should use throws keyword to let the caller know about the checked exceptions that might be thrown from the method. Unchecked Exceptions are not required to be handled in the program or to mention them in the throws clause of the method.
   2. Exception is the superclass of all checked exceptions whereas is the superclass of all unchecked exceptions. Note that RuntimeException is the child class of Exception.
   3. Checked exceptions are error scenarios that require to be handled in the code, or else you will get compile time error. For example, if you use FileReader to read a file, it throws and we must catch it in the try-catch block or throw it again to the caller method. Unchecked exceptions are mostly caused by poor programming, for example, NullPointerException when invoking a method on an object reference without making sure that it’s not null. For example, I can write a method to remove all the vowels from the string. It’s the caller responsibility to make sure not to pass a null string. I might change the method to handle these scenarios but ideally, the caller should take care of this.

What is the difference between throw and throws keyword in Java?

1. throws keyword is used with method signature to declare the exceptions that the method might throw whereas throw keyword is used to disrupt the flow of program and handing over the exception object to runtime to handle it.

How to write custom exception in Java?

1. We can extend Exception class or any of it’s subclasses to create our custom exception class. The custom exception class can have it’s own variables and methods that we can use to pass error codes or other exception related information to the exception handler.
   A simple example of a custom exception is shown below.

   
   package com.journaldev.exceptions;
   
   import java.io.IOException;
   
   public class MyException extends IOException {
   
    private static final long serialVersionUID = 4664456874499611218L;
    
    private String errorCode="Unknown_Exception";
    
    public MyException(String message, String errorCode){
     super(message);
     this.errorCode=errorCode;
    }
    
    public String getErrorCode(){
     return this.errorCode;
    }
    
   
   }
   

Java exception handling interview questions

What is OutOfMemoryError in Java?

1. OutOfMemoryError in Java is a subclass of java.lang.VirtualMachineError and it’s thrown by JVM when it ran out of heap memory. We can fix this error by providing more memory to run the java application through java options.
   $>java MyProgram -Xms1024m -Xmx1024m -XX:PermSize=64M -XX:MaxPermSize=256m

What are different scenarios causing “Exception in thread main”?

1. Some of the common main thread exception scenarios are:
   • Exception in thread main java.lang.UnsupportedClassVersionError: This exception comes when your java class is compiled from another JDK version and you are trying to run it from another java version.
   • Exception in thread main java.lang.NoClassDefFoundError: There are two variants of this exception. The first one is where you provide the class full name with .class extension. The second scenario is when Class is not found.
   • Exception in thread main java.lang.NoSuchMethodError: main: This exception comes when you are trying to run a class that doesn’t have the main method.
   • Exception in thread “main” java.lang.ArithmeticException: Whenever an exception is thrown from the main method, it prints the exception is console. The first part explains that exception is thrown from the main method, second part prints the exception class name and then after a colon, it prints the exception message.

What is the difference between final, finally and finalize in Java?

1. final and finally are keywords in Java whereas finalize is a method.
   final keyword can be used with class variables so that they can’t be reassigned, with class to avoid extending by classes and with methods to avoid overriding by subclasses, finally keyword is used with try-catch block to provide statements that will always get executed even if some exception arises, usually finally is used to close resources. finalize() method is executed by Garbage Collector before the object is destroyed, it’s a great way to make sure all the global resources are closed.
   Out of the three, only finally is related to java exception handling.

What happens when an exception is thrown by the main method?

1. When an exception is thrown by a main() method, Java Runtime terminates the program and print the exception message and stack trace in the system console.

Can we have an empty catch block?

1. We can have an empty catch block but it’s the example of worst programming. We should never have empty catch block because if the exception is caught by that block, we will have no information about the exception and it will be a nightmare to debug it. There should be at least a logging statement to log the exception details in console or log files.

Provide some Java Exception Handling Best Practices?

1. Some of the best practices related to Java Exception Handling are:
   • Use Specific Exceptions for ease of debugging.
   • Throw Exceptions Early (Fail-Fast) in the program.
   • Catch Exceptions late in the program, let the caller handle the exception.
   • Use Java 7 ARM feature to make sure resources are closed or use finally block to close them properly.
   • Always log exception messages for debugging purposes.
   • Use a multi-catch block for the cleaner close.
   • Use custom exceptions to throw a single type of exception from your application API.
   • Follow naming convention, always end with Exception.
   • Document the Exceptions Thrown by a method using @throws in Javadoc.
   • Exceptions are costly, so throw it only when it makes sense. Else you can catch them and provide a null or empty response.

What is the problem with below programs and how do we fix it?

1. In this section, we will look into some programming questions related to java exceptions.
   1. What is the problem with below program?

      
      package com.journaldev.exceptions;
      
      import java.io.FileNotFoundException;
      import java.io.IOException;
      
      public class TestException {
      
       public static void main(String[] args) {
        try {
         testExceptions();
        } catch (FileNotFoundException | IOException e) {
         e.printStackTrace();
        }
       }
       
       
       
       public static void testExceptions() throws IOException, FileNotFoundException{
        
       }
      }
      

      Above program won’t compile and you will get an error message as “The exception FileNotFoundException is already caught by the alternative IOException”. This is because FileNotFoundException is a subclass of IOException, there are two ways to solve this problem.
      The first way is to use a single catch block for both the exceptions.

      
        try {
         testExceptions();
        }catch(FileNotFoundException e){
         e.printStackTrace();
        }catch (IOException  e) {
         e.printStackTrace();
        }
      

      Another way is to remove the FileNotFoundException from the multi-catch block.

      
        try {
         testExceptions();
        }catch (IOException  e) {
         e.printStackTrace();
        }
      

      You can choose any of these approach based on your catch block code.
   2. What is the problem with below program?

      
      package com.journaldev.exceptions;
      
      import java.io.FileNotFoundException;
      import java.io.IOException;
      
      import javax.xml.bind.JAXBException;
      
      public class TestException1 {
      
       public static void main(String[] args) {
         try {
          go();
         } catch (IOException e) {
          e.printStackTrace();
         } catch (FileNotFoundException e) {
          e.printStackTrace();
         } catch (JAXBException e) {
          e.printStackTrace();
         }
       }
      
       public static void go() throws IOException, JAXBException, FileNotFoundException{
        
       }
      }
      

      The program won’t compile because FileNotFoundException is a subclass of IOException, so the catch block of FileNotFoundException is unreachable and you will get an error message as “Unreachable catch block for FileNotFoundException. It is already handled by the catch block for IOException”.
      You need to fix the catch block order to solve this issue.

      
         try {
          go();
         } catch (FileNotFoundException e) {
          e.printStackTrace();
         } catch (IOException e) {
          e.printStackTrace();
         } catch (JAXBException e) {
          e.printStackTrace();
         }
      

      Notice that JAXBException is not related to IOException or FileNotFoundException and can be put anywhere in above catch block hierarchy.
   3. What is the problem with the below program?

      
      package com.journaldev.exceptions;
      
      import java.io.IOException;
      
      import javax.xml.bind.JAXBException;
      
      public class TestException2 {
      
       public static void main(String[] args) {
        try {
         foo();
        } catch (IOException e) {
         e.printStackTrace();
        }catch(JAXBException e){
         e.printStackTrace();
        }catch(NullPointerException e){
         e.printStackTrace();
        }catch(Exception e){
         e.printStackTrace();
        }
       }
      
       public static void foo() throws IOException{
        
       }
      }
      

      The program won’t compile because JAXBException is a checked exception and foo() method should throw this exception to catch in the calling method. You will get an error message as “Unreachable catch block for JAXBException. This exception is never thrown from the try statement body”.To solve this issue, you will have to remove the catch block of JAXBException.Notice that catching NullPointerException is valid because it’s an unchecked exception.
   4. What is the problem with below program?

      
      package com.journaldev.exceptions;
      
      public class TestException3 {
      
       public static void main(String[] args) {
        try{
        bar();
        }catch(NullPointerException e){
         e.printStackTrace();
        }catch(Exception e){
         e.printStackTrace();
        }
        
        foo();
       }
      
       public static void bar(){
        
       }
       
       public static void foo() throws NullPointerException{
        
       }
      }
      

      This is a trick question, there is no problem with the code and it will compile successfully. We can always catch Exception or any unchecked exception even if it’s not in the throws clause of the method.
      Similarly, if a method (foo) declares the unchecked exception in the throws clause, it is not mandatory to handle that in the program.
   5. What is the problem with below program?

      
      package com.journaldev.exceptions;
      
      import java.io.IOException;
      
      public class TestException4 {
      
       public void start() throws IOException{  
       }
       
       public void foo() throws NullPointerException{
        
       }
      }
      
      class TestException5 extends TestException4{
       
       public void start() throws Exception{
       }
       
       public void foo() throws RuntimeException{
        
       }
      }
      

      The above program won’t compile because the start() method signature is not the same in a subclass. To fix this issue, we can either change the method signature in the subclass to be exactly the same as the superclass or we can remove the throws clause from the subclass method as shown below.

      
      @Override
       public void start(){
       }
      

   6. What is the problem with below program?

      
      package com.journaldev.exceptions;
      
      import java.io.IOException;
      
      import javax.xml.bind.JAXBException;
      
      public class TestException6 {
      
       public static void main(String[] args) {
        try {
         foo();
        } catch (IOException | JAXBException e) {
         e = new Exception("");
         e.printStackTrace();
        }catch(Exception e){
         e = new Exception("");
         e.printStackTrace();
        }
       }
      
       public static void foo() throws IOException, JAXBException{
        
       }
      }
      

      The above program won’t compile because exception object in the multi-catch block is final and we can’t change its value. You will get the compile-time error as “The parameter e of a multi-catch block cannot be assigned”.