Michael Voss created LOG4J2-3435: ------------------------------------ Summary: Possibly invalid module-info.class in jog4j-api-2-17.1.jar Key: LOG4J2-3435 URL: https://issues.apache.org/jira/browse/LOG4J2-3435 Project: Log4j 2 Issue Type: Bug Components: API Affects Versions: 2.17.1 Environment: SAP WEB AS 7.50.20 (AIX) JVM 1.8 (SAP JVM) Reporter: Michael Voss Attachments: module-info.class
When deploying an application containing log4j-api-2.17.1.jar retrieved via maven dependency {code:xml} <dependency> <groupId>org.apache.logging.log4j</groupId> <artifactId>log4j-api</artifactId> <version>2.17.1</version> </dependency> {code} onto a SAP WebApplicationServer running Java 8.1, the deployment (using NWDI) fails reporting {code} com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException. ... Caused by: com.sap.engine.library.bytecode.cf.CFException: Invalid constant pool tag, 19 at index 5. {code} This error is thrown due to an alleged java version conflict, although log4j 2.17.1 requires Java 8 only and the application server (and it's deployment mechanism) is running on Java 8. After evaluating the feedback from SAP support, it seems the attached file {{module-info.class}} located in {{log4j-api-2.17.1.jar/META-INF/versions/9/}} is the reason for this behaviour. If we remove this file from the jar, the deployment is successful. -- This message was sent by Atlassian Jira (v8.20.1#820001)