Why custom exceptions are needed in Java - Performance Analysis

Time Complexity: Why custom exceptions are needed

O(n)

Understanding Time Complexity

We want to understand how the time cost changes when using custom exceptions in Java.

How does adding custom exceptions affect the program's running time as input grows?

Scenario Under Consideration

Analyze the time complexity of this code snippet using a custom exception.

public class CustomException extends Exception {
    public CustomException(String message) {
        super(message);
    }
}

public void checkValue(int value) throws CustomException {
    if (value < 0) {
        throw new CustomException("Negative value not allowed");
    }
}
    

This code defines a custom exception and throws it when a value is negative.

Identify Repeating Operations

Look for repeated checks or exception throws.

• Primary operation: Checking the value and possibly throwing the exception.
• How many times: Once per call to checkValue.

How Execution Grows With Input

Each time we call checkValue, it does one check and maybe throws an exception.

Input Size (n)	Approx. Operations
10	10 checks, some exceptions
100	100 checks, some exceptions
1000	1000 checks, some exceptions

Pattern observation: The number of operations grows directly with the number of calls.

Final Time Complexity

Time Complexity: O(n)

This means the time grows linearly with how many times you check values and possibly throw exceptions.

Common Mistake

[X] Wrong: "Using custom exceptions makes the program slower in a way that grows faster than linearly."

[OK] Correct: Each exception check is simple and happens once per call, so time grows linearly, not faster.

Interview Connect

Understanding how custom exceptions affect time helps you explain your code's behavior clearly and confidently in interviews.

Self-Check

What if we added a loop inside checkValue that checks multiple values before throwing an exception? How would the time complexity change?

Practice

1. Why do we need custom exceptions in Java?
public class MyException extends Exception {}

easy

A. To avoid using try-catch blocks

B. To replace all built-in exceptions with new ones

C. To make the program run faster

D. To create specific error types that describe unique problems

Solution

1. Step 1: Understand the purpose of custom exceptions

   Custom exceptions allow programmers to define errors that are specific to their application's needs, making error handling clearer.

2. Step 2: Compare with other options

   Replacing all built-in exceptions or avoiding try-catch blocks is not the goal. Custom exceptions do not improve speed directly.

3. Final Answer:

   To create specific error types that describe unique problems -> Option D

4. Quick Check:

   Custom exceptions = Specific error types [OK]

Hint: Custom exceptions describe unique problems clearly [OK]

Common Mistakes:

• Thinking custom exceptions speed up the program
• Believing they replace all built-in exceptions
• Assuming they remove the need for try-catch

2. Which of the following is the correct way to declare a custom checked exception in Java?

easy

A. class MyException extends RuntimeException {}

B. class MyException extends Error {}

C. class MyException extends Exception {}

D. class MyException extends Throwable {}

Solution

1. Step 1: Identify checked exceptions

   Checked exceptions in Java must extend Exception but not RuntimeException.

2. Step 2: Analyze each option

   Extending RuntimeException creates an unchecked exception. Extending Error is for system errors. Extending Exception creates a checked exception. Extending Throwable is too general.

3. Final Answer:

   class MyException extends Exception {} -> Option C

4. Quick Check:

   Checked exceptions extend Exception [OK]

Hint: Checked exceptions extend Exception class [OK]

Common Mistakes:

• Confusing checked and unchecked exceptions
• Extending Error instead of Exception
• Extending Throwable directly

3. What will be the output of this code?

class MyException extends Exception {}

public class Test {
  public static void check(int num) throws MyException {
    if (num < 0) throw new MyException();
    else System.out.println("Number is " + num);
  }

  public static void main(String[] args) {
    try {
      check(-5);
    } catch (MyException e) {
      System.out.println("Caught MyException");
    }
  }
}

medium

A. Caught MyException

B. Number is -5

C. Compilation error

D. No output

Solution

1. Step 1: Understand the check method behavior

   If the number is less than 0, it throws MyException. Since -5 < 0, exception is thrown.

2. Step 2: Analyze main method's try-catch

   The exception is caught in the catch block, which prints "Caught MyException".

3. Final Answer:

   Caught MyException -> Option A

4. Quick Check:

   Exception thrown and caught = "Caught MyException" [OK]

Hint: Exception thrown for negative, caught prints message [OK]

Common Mistakes:

• Expecting negative number print instead of exception
• Thinking code won't compile due to throws
• Missing catch block effect

4. Identify the error in this custom exception class:

public class MyException extends Exception {
  public MyException(String message) {
    super();
  }
}

medium

A. Class should extend RuntimeException instead

B. Missing call to super(message) in constructor

C. Constructor should not have parameters

D. No error, code is correct

Solution

1. Step 1: Check constructor call to superclass

   The constructor takes a message but calls super() without passing it, so the message is lost.

2. Step 2: Correct usage of super constructor

   It should call super(message) to pass the error message to the Exception class.

3. Final Answer:

   Missing call to super(message) in constructor -> Option B

4. Quick Check:

   Pass message to super constructor [OK]

Hint: Pass message to super() in constructor [OK]

Common Mistakes:

• Calling super() without message
• Changing exception type unnecessarily
• Removing constructor parameters

5. You want to create a custom exception that handles invalid user input differently from other errors. Which approach best supports this goal?

hard

A. Create a custom exception class extending Exception and catch it separately

B. Use only built-in exceptions and catch all in one block

C. Throw RuntimeException with a custom message

D. Avoid exceptions and use error codes instead

Solution

1. Step 1: Understand the need for specific error handling

   To handle invalid input differently, a distinct exception type is needed.

2. Step 2: Choose the best design

   Creating a custom exception extending Exception allows catching it separately and handling it clearly.

3. Final Answer:

   Create a custom exception class extending Exception and catch it separately -> Option A

4. Quick Check:

   Custom exception + separate catch = clear handling [OK]

Hint: Custom exception + separate catch block for clarity [OK]

Common Mistakes:

• Using only built-in exceptions for all errors
• Throwing RuntimeException without clarity
• Avoiding exceptions and complicating code