Skip to content

Conversation

@philipwhiuk
Copy link
Contributor

If the application runs out of memory then a OutOfMemoryError will be thrown. This extends Throwable and not Exception.
Trying to catch this and log is rarely useful.
There are other such errors like this which are rarely possible to 'handle' and keep going.

CompositeLog (and other such places) should stick to catching Exceptions which are programming errors, rather than indicates of platform problems.

@chrjohn chrjohn changed the title Catch Exception not Throwable Catch Exception not Throwable in CompositeLog Jan 3, 2025
@chrjohn chrjohn added this to the QFJ 3.0.0 milestone Jan 3, 2025
@chrjohn chrjohn merged commit 8bfaf28 into quickfix-j:master Jan 3, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants