Hi Team, Can you please help us to fix this issue.
Regards, Guru. From: Dominik Psenner <dpsen...@gmail.com> Sent: 04 March 2023 02:16 To: secur...@logging.apache.org Cc: Paolo Gil Ostrea <post...@simeio.com>; Roark Hamilton <rhamil...@simeio.com>; Gurumoorthi Vijayalingam <gvijayalin...@simeio.com> Subject: [External] Re: Log4j Issue CAUTION: This message was sent from outside of the company. Please do not click links or open attachments unless you recognize the source of this email and know the content is safe. Hi I'm CCing the original author of the message. Please read below. Further please consider posting to the proper mailing list. The request is not about a security issue and probably should have been posted to dev@logging.apache.org<mailto:dev@logging.apache.org> after subscribing to that mailing list. Warm regards Dominik -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Fri, Mar 3, 2023, 21:17 Piotr P. Karwasz <piotr.karw...@gmail.com<mailto:piotr.karw...@gmail.com>> wrote: Gurumoorthi, On Fri, 3 Mar 2023 at 19:04, Gurumoorthi Vijayalingam <gvijayalin...@simeio.com<mailto:gvijayalin...@simeio.com>> wrote: > Just attached the error message and log4j configuration for your reference. MapLookup#newMap changed from private (as in 2.2) to package (as in 2.17.1) in the course of history. Your Tomcat is picking up the private one, which means that log4j-core-2.2.jar is still on the classpath. Double check that the old Log4j2 version are no longer there and restart Tomcat to be sure. Piotr
