ppkarwasz commented on issue #3622: URL: https://github.com/apache/logging-log4j2/issues/3622#issuecomment-2830306605
@sadmanmd, How to handle _partial_ configuration startup failures is currently a grey area in Log4j Core. We [discussed this recently on `dev@logging`](https://lists.apache.org/thread/h2oydyk6xld47ljttqvflbt4530o73vw) and the consensus is that in cases like yours the whole `Configuration` object should be discarded and the old configuration should be used (or the default configuration if the first configuration fails). Would this be an acceptable solution? The configuration problem you present in this issue is not a temporary problem accessing a resource, but a permanent one. IMHO it should either prevent the configuration from being used at all or propagate an exception to the caller (we can create a [configuration property](https://logging.apache.org/log4j/2.x/manual/systemproperties.html) for this). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
