ppkarwasz commented on issue #3836: URL: https://github.com/apache/logging-log4j2/issues/3836#issuecomment-3094645747
Hi @rschmitt, Thank you for reporting this. The behavior you're seeing stems from the fact that the **Java Properties configuration format** operates differently from the standard configuration formats (XML, JSON, YAML). It has evolved more in response to user requests than from adherence to the design principles followed by the other formats. The fact that `PropertiesConfigurationBuilder` throws an exception instead of returning `null` on configuration errors is a known issue — see #3088. Version `2.25.0` didn’t fundamentally change that behavior, but it did extend it somewhat as a side effect of #3703. Now, configurations containing invalid or unrecognized content (outside of recognized prefixes like `appender`, `logger`, etc.) also result in exceptions. While fixing #3088 remains on the table, recent [discussion on the `dev@logging` list](https://lists.apache.org/thread/h2oydyk6xld47ljttqvflbt4530o73vw) suggests that the direction we're leaning toward is actually the opposite — namely, **moving toward a stricter, fail-fast model**. That means configuration errors would consistently cause the entire configuration to fail, rather than silently falling back or continuing with missing components (while only logging `WARN` messages). So while this behavior may seem abrupt or inconsistent today, it aligns more closely with where the project is headed in terms of robustness and transparency in configuration handling. If you have thoughts or feedback on the proposal above, you're welcome to share them either by replying to the [`dev@logging` mailing list thread](https://lists.apache.org/thread/h2oydyk6xld47ljttqvflbt4530o73vw) or by posting your remarks here. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
