Github user leventov commented on the issue:
https://github.com/apache/logging-log4j2/pull/87
@remkop
> MemoryMappedFileManager::switchRegion and
::closeAndSwitchRegionWhileLocked should not throw Error: generally a logging
problem should not bring down the application. See also the
{{ignoreExceptions}}
[configuration|https://logging.apache.org/log4j/2.x/manual/appenders.html#MemoryMappedFileAppender]
attribute that allows applications to choose to receive logging exceptions.
I follow the approach of java.util.concurrent internals here, where `throw
new Error(...)` is used in the face of unrecoverable and totally unexpected
errors. the alternative is `AssertionError`, or `assert` statements.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
