Home › Java exceptions › InvocationTargetException

What it looks like

java.lang.reflect.InvocationTargetException
Caused by: java.lang.IllegalArgumentException: invalid id

Extends ReflectiveOperationException in java.lang.reflect.

What it means

When code calls a method with Method.invoke (or a framework does, to run your controller, listener or test), any exception thrown by the target method is wrapped in InvocationTargetException. The wrapper has no message of its own; the useful information is in getTargetException() or getCause(). Many frameworks unwrap it for you, but when you see it in a log, skip to the Caused by line.

Common causes

• The target method threw any exception, checked or unchecked.
• A framework invoking lifecycle callbacks (@PostConstruct, @EventListener, JUnit test methods).
• Your own reflection or proxy code that does not unwrap the exception.
• A bug in the reflected method, such as a NullPointerException on a missing field.

How to fix it

1. Read the nested cause and fix that exception.
2. In your reflection code, catch InvocationTargetException and rethrow e.getCause().
3. Prefer method handles or interfaces to reflection when you can.
4. Log the full chain so the root cause is not hidden.

Broken and fixed

try { m.invoke(bean); }
catch (InvocationTargetException e) { throw new RuntimeException(e); } // wrapper hides intent

try { m.invoke(bean); }
catch (InvocationTargetException e) {
    throw e.getCause() instanceof RuntimeException re ? re : new RuntimeException(e.getCause());
}

🔎 Unravel the failing code 🔎 Unravel the fix

In Spring and enterprise code

Spring wraps startup failures from @PostConstruct methods the same way; the bean creation error lists the real cause at the bottom.

Debug it faster

Paste the whole stack trace into the stack trace beautifier to hide framework frames, jump to the root cause and find the first line of your own code. It runs in your browser, so the trace never leaves your machine.

Related exceptions