ramanathan1504 commented on issue #4047: URL: https://github.com/apache/logging-log4j2/issues/4047#issuecomment-3890710860
@gryn-alina Based on the latest comment, this appears to be related to #3947, which was fixed in Log4j 2.25.3. The original stack trace shows 2.25.1 was being used at runtime, which explains the SslConfiguration NPE. After upgrading to 2.25.3 and explicitly configuring the <Ssl> element (e.g., providing a <TrustStore>), the issue was resolved. Given this, it seems the problem was due to the older version and configuration requirements rather than a new defect in Log4j. It may be appropriate to close this issue as resolved (fixed in 2.25.3). right? -- 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]
