Confusion about "eating an exception" (in Java)?

Question

What exactly is eating an exception? Is it when there's nothing in the catch block or when you don't log the exception?

I understand that this is eating an exception.

try {
//exception code
} catch (Exception e) {
}

However, what about this?

try {
//exception code
} catch (Exception e) {
System.out.println("Exception Thrown");
}

this will answer your question https://stackoverflow.com/q/3972887/9942608 — Himanshi Thakur, Apr 26 '21 at 11:46
Does this answer your question? [Eating Exceptions](https://stackoverflow.com/questions/3972887/eating-exceptions) — Himanshi Thakur, Apr 26 '21 at 11:46

score 1 · Accepted Answer · answered Apr 26 '21 at 08:07

When there is nothing in the catch block.

In general it is necessary to catch the more specific exception if it is possible to recover that exception and if not log the exception and rethrown it.

A program that "eat" exception is a bad practice because could be in an inconsistent state.

Confusion about "eating an exception" (in Java)?

1 Answers1