It appears that this is from a proprietary product so I don’t have access to their source code. You only have a couple of options: 1. Decompile the AgentDebugger class and the portion of AuthSessionFactory that calls it and provide that to us so we can identify why it needs this. However, that might violate whatever license agreement you have with RSA. 2. Contact RSA and report this issue.
I can’t be sure but it almost looks like RSA has implemented their own Log4j 1.x implementation. If that indeed is the case then there is no way a Log4j 2 compatibility layer is going to support that. Ralph > On Nov 10, 2021, at 6:49 AM, EDMONDO SENA <edse...@gmail.com> wrote: > > In log4j2 the LocationInfo where is it? > > The exception is: > > at com.rsa.authagent.authapi.logger.AgentDebugger.formatLocationMsg > at com.rsa.authagent.authapi.logger.AgentDebugger.log > at com.rsa.authagent.authapi.logger.AgentDebugger.trace > at com.rsa.authagent.authapi.AuthSessionFactory.a > at com.rsa.authagent.authapi.AuthSessionFactory.<init> > at com.rsa.authagent.authapi.AuthSessionFactory.getInstance() > ...... > at ......common.library.rsa.RSAConnection.<init> > at ......common.library.rsa.RSAConnection.getInstance(RSAConnection.java) > > > Thanks. > //Edmondo. > > > > > Il giorno gio 4 nov 2021 alle ore 08:33 Ralph Goers < > ralph.go...@dslextreme.com> ha scritto: > >> You are correct that there is no LocationInfo constructor. Unfortunately, >> we can’t really help here without more information. >> >> 1. I am assuming this is Auth0’s AuthAPI? I don’t even see them reference >> any logging framework. >> 2. If it is brought in by a dependency we would need to see the stack >> trace to determine what is doing it to help you fix it. >> 3. We would need the stack trace to figure out what the caller is doing >> and why they need the LocationInfo. >> >> So without the stack trace we don’t have any info to determine what the >> problem is. >> >> Ralph >> >>> On Nov 3, 2021, at 1:20 AM, EDMONDO SENA <edse...@gmail.com> wrote: >>> >>> Specifically, the LocationInfo constructor that is called by the 3pp lib >> does not exist in the new library. >>> >>> >>> >>> >>> Il giorno ven 29 ott 2021 alle ore 17:43 Gary Gregory < >> garydgreg...@gmail.com <mailto:garydgreg...@gmail.com>> ha scritto: >>> What is the complete stack trace? >>> >>> Gary >>> >>> On Fri, Oct 29, 2021, 11:37 EDMONDO SENA <edse...@gmail.com <mailto: >> edse...@gmail.com>> wrote: >>> >>>> There are no log4j1 jars in classpath. >>>> >>>> //Edmondo. >>>> >>>> >>>> >>>> Il giorno ven 29 ott 2021 alle 17:34 Doug Wegscheid < >>>> dwegsch...@sbcglobal.net <mailto:dwegsch...@sbcglobal.net>> ha >> scritto: >>>> >>>>> ...and make sure that the log4j v1 jar files are NOT on the >> classpath. >>>>> >>>>> On Friday, October 29, 2021, 11:21:52 AM EDT, Gary Gregory < >>>>> garydgreg...@gmail.com <mailto:garydgreg...@gmail.com>> wrote: >>>>> >>>>> Make sure the log4j 2 jars are first on the class path and do not >>>> include >>>>> any log4j 1 jars. >>>>> >>>>> Gary >>>>> >>>>> On Fri, Oct 29, 2021, 11:18 EDMONDO SENA <edse...@gmail.com <mailto: >> edse...@gmail.com>> wrote: >>>>> >>>>>> >>>>>> it has already been done and it doesn't work! >>>>>> >>>>>> This is the exception: >>>>>> >>>>>> Exception in thread "main" >>>>>> >> Java.lang.NoSuchMethodError:org.apache.log4j.spi.LocationInfo.<init> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 2021/10/29 15:09:59, Doug Wegscheid <dwegsch...@sbcglobal.net >> <mailto:dwegsch...@sbcglobal.net>> >>>> wrote: >>>>>>> Put the log4j-1.2-api.jar on the classpath along with the other >>>>>> necessary log4j2 jars, and configure log4j2. >>>>>>> >>>>>>> Sent from AT&T Yahoo Mail on Android >>>>>>> >>>>>>> On Fri, Oct 29, 2021 at 11:07 AM, EDMONDO SENA< >> edse...@gmail.com <mailto:edse...@gmail.com>> >>>>>> wrote: it's not that simple one, a thing is to write, one thing >> is to >>>>>> understand what to do! Said so it seems a simplistic discussion. >>>>>>> >>>>>>> //Edmondo. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 2021/10/29 14:13:31, Doug Wegscheid <dwegsch...@sbcglobal.net >> <mailto:dwegsch...@sbcglobal.net>> >>>>>> wrote: >>>>>>>> You can your existing authapi.jar: >>>>>>>> "Log4j 2 provides support for the Log4j 1 logging methods by >>>>> providing >>>>>> alternate implementations of the classes containing those methods. >>>> These >>>>>> classes may be found in the log4j-1.2-api jar distributed with the >>>>> project. >>>>>> All calls to perform logging will result in the data passed to the >>>>> logging >>>>>> methods to be forwarded to the Log4j2 API where they can be >> processed >>>> by >>>>>> implementations of the Log4j 2 API." >>>>>>>> >>>>>>>> Sent from AT&T Yahoo Mail on Android >>>>>>>> >>>>>>>> On Fri, Oct 29, 2021 at 9:04 AM, EDMONDO SENA< >> edse...@gmail.com <mailto:edse...@gmail.com>> >>>>>> wrote: I have already seen this site but I have not found any >> answer >>>> to >>>>> my >>>>>> problem. >>>>>>>> >>>>>>>> //Edmondo. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 2021/10/29 12:52:55, Gary Gregory <garydgreg...@gmail.com >> <mailto:garydgreg...@gmail.com>> >>>> wrote: >>>>>>>>> Edmondo, >>>>>>>>> >>>>>>>>> Please see >>>>>> https://logging.apache.org/log4j/2.x/manual/compatibility.html < >> https://logging.apache.org/log4j/2.x/manual/compatibility.html> >>>>>>>>> >>>>>>>>> Gary >>>>>>>>> >>>>>>>>> On Fri, Oct 29, 2021, 04:22 EDMONDO SENA <edse...@gmail.com >> <mailto:edse...@gmail.com>> >>>>> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Good Morning, >>>>>>>>>> >>>>>>>>>> authapi.jar is a 3pp library which uses old log4 inside. >>>>>>>>>> Is there any way to get authapi.jar to work with log4j 2? >>>>>>>>>> >>>>>>>>>> What can I do to make them work together? >>>>>>>>>> Do I need to download a new authapi.jar version for log4j2? >>>>>>>>>> >>>>>>>>>> Thanks in advance. >>>>>>>>>> Kind regards. >>>>>>>>>> >>>>>>>>>> //Edmondo. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>> >> --------------------------------------------------------------------- >>>>>>>>>> To unsubscribe, e-mail: >>>>> log4j-user-unsubscr...@logging.apache.org <mailto: >> log4j-user-unsubscr...@logging.apache.org> >>>>>>>>>> For additional commands, e-mail: >>>>>> log4j-user-h...@logging.apache.org <mailto: >> log4j-user-h...@logging.apache.org> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: >> log4j-user-unsubscr...@logging.apache.org <mailto: >> log4j-user-unsubscr...@logging.apache.org> >>>>>>>> For additional commands, e-mail: >>>> log4j-user-h...@logging.apache.org <mailto: >> log4j-user-h...@logging.apache.org> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: >> log4j-user-unsubscr...@logging.apache.org <mailto: >> log4j-user-unsubscr...@logging.apache.org> >>>>>>> For additional commands, e-mail: >> log4j-user-h...@logging.apache.org <mailto: >> log4j-user-h...@logging.apache.org> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org >> <mailto:log4j-user-unsubscr...@logging.apache.org> >>>>>> For additional commands, e-mail: >> log4j-user-h...@logging.apache.org <mailto: >> log4j-user-h...@logging.apache.org> >>>>>> >>>>>> >>>>> >>>> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
