Hi Team, We tried the steps as Christian mentioned in below email, but still getting same error. Please help us to fix this issue
Thanks, Guru. -----Original Message----- From: Christian Grobmeier <[email protected]> Sent: Tuesday, March 21, 2023 2:17 AM To: Gurumoorthi Vijayalingam <[email protected]>; [email protected] Cc: Paolo Gil Ostrea <[email protected]>; Roark Hamilton <[email protected]>; Bhavana Pujari <[email protected]>; Sireesha Kutala <[email protected]> Subject: Re: [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. Hello Gurumoorthi, Piotr already responded to your email: > 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 If this information does not help you, respond to [email protected] as Dominik told you. Kind regards, Christian -- The Apache Software Foundation V.P., Data Privacy On Mon, Mar 20, 2023, at 17:27, Gurumoorthi Vijayalingam wrote: > Hi Team, > > Can you please help us to fix this issue. > > Regards, > Guru. > > From: Dominik Psenner <[email protected]> > Sent: 04 March 2023 02:16 > To: [email protected] > Cc: Paolo Gil Ostrea <[email protected]>; Roark Hamilton > <[email protected]>; Gurumoorthi Vijayalingam > <[email protected]> > 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 [email protected]<mailto:[email protected]> 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 > <[email protected]<mailto:[email protected]>> wrote: > Gurumoorthi, > > On Fri, 3 Mar 2023 at 19:04, Gurumoorthi Vijayalingam > <[email protected]<mailto:[email protected]>> 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
