aaaygupta commented on issue #2737: URL: https://github.com/apache/logging-log4j2/issues/2737#issuecomment-2235891534
> > My guess is that J9 version 26 can not handle the static initialization cycle that starts with the `StatusLogger` class. > > To initialize `StatusLogger`, you need to initialize its parent class `AbstractLogger`. The initialization of `AbstractLogger` causes `DefaultLogBuilder` to be initialized: > > https://github.com/apache/logging-log4j2/blob/05f9d96b95e2c227b263650441c6bc5207914858/log4j-api/src/main/java/org/apache/logging/log4j/spi/AbstractLogger.java#L106 > > > > which starts the initialization of `StatusLogger`. > > Most modern JVM handle this cycle correctly (I tested the latest Semuru OpenJ9 8 release), but J9 version 26 must not be among them. > > @aaaygupta, Can you upgrade the virtual machine used by DB2 to a more recent version of Semuru? > > Appologies for silly queries as I am new with IBM java. How did you say that the java that I am using is " J9 version 26" can you highlight that. Also when you said that "J9 version 26 can not handle the static initialization cycle that starts with the StatusLogger class" then is it something introduced in log4j 2.23.1? Because same sample works in same environment when I use log4j 2.23.0 jars Hi, The issue got resolved after upgrading to IBM java 8 to its latest updated version of Semuru **(8.0.412.0 OpenJDK 8u412-b08 OpenJ9 0.44.0)** But it seems this jdk do not have all the required IBM DB2 specific jars. As I got another **classnotfoundexception "com.ibm.xml.xlxp.api.jaxp.impl.SAXParserFactoryImpl"** When I compared the two jdks there were many jars that were missing. Any opinion on this? -- 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]
