We had to do a workaround in our internal test suites by setting a system property to trick this thing into not running; Maybe we can apply that also here...
On Fri, Mar 18, 2022 at 3:12 PM Dawid Weiss <[email protected]> wrote: > > I think this is Amazon trying to cope with log4shell - they've added > external instrumentation. > > On Fri, Mar 18, 2022 at 7:51 PM Robert Muir <[email protected]> wrote: > > > > >> 2> at > > >> java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > > >> 2> at Log4jHotPatch.asmVersion(Log4jHotPatch.java:71) > > >> 2> at Log4jHotPatch.agentmain(Log4jHotPatch.java:93) > > >> 2> ... 6 more > > > > > > > > > Does anyone have an idea? > > > > > > > Your JVM is broken, look at this Log4jHotPatch stuff causing trouble. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
