-
Enhancement
-
Resolution: Done
-
Major
-
None
When upgrading JBoss EAP for OpenShift from 7.1 to 7.2 or later, and if we bring 7.1-based standalone-openshift.xml into 7.2 or later, the container fails to start with the following error:
06:10:28,452 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "logging"), ("custom-formatter" => "OPENSHIFT") ]): java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager.ext" for formatter "OPENSHIFT" at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65) [jboss-logmanager-2.1.14.Final-redhat-00001.jar:2.1.14.Final-redhat-00001] at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30) [jboss-logmanager-2.1.14.Final-redhat-00001.jar:2.1.14.Final-redhat-00001] at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172) [jboss-logmanager-2.1.14.Final-redhat-00001.jar:2.1.14.Final-redhat-00001] at org.jboss.as.logging.logmanager.ConfigurationPersistence.addFormatterConfiguration(ConfigurationPersistence.java:215) at org.jboss.as.logging.formatters.CustomFormatterResourceDefinition$2.performRuntime(CustomFormatterResourceDefinition.java:113) at org.jboss.as.logging.LoggingOperations$LoggingAddOperationStepHandler.performRuntime(LoggingOperations.java:186) at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:338) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:159) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1413) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:521) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:472) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:434) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.server.ServerService.boot(ServerService.java:435) [wildfly-server-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.server.ServerService.boot(ServerService.java:394) [wildfly-server-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:374) [wildfly-controller-10.1.2.SP1-redhat-00001.jar:10.1.2.SP1-redhat-00001] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_242] Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.logmanager.ext at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:297) [jboss-modules.jar:1.9.1.Final-redhat-00001] at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:283) [jboss-modules.jar:1.9.1.Final-redhat-00001] at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:560) [jboss-logmanager-2.1.14.Final-redhat-00001.jar:2.1.14.Final-redhat-00001] at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63) [jboss-logmanager-2.1.14.Final-redhat-00001.jar:2.1.14.Final-redhat-00001] ... 18 more 06:10:28,519 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
This issue is considered as breaking compatibility, but it's not mentioned in Getting Started with JBoss EAP for OpenShift Container Platform in 1.4. Version Compatibility and Support and Release Notes. Incompatibility information between minor versions should be described in the product documentation.
The workaround is to fix standalone-openshift.xml as follows:
--- a/test-app/configuration/standalone-openshift.xml +++ b/test-app/configuration/standalone-openshift.xml @@ -87,7 +87,7 @@ </access-control> </management> <profile> - <subsystem xmlns="urn:jboss:domain:logging:3.0"> + <subsystem xmlns="urn:jboss:domain:logging:8.0"> <console-handler name="CONSOLE"> <formatter> <named-formatter name="##CONSOLE-FORMATTER##"/> @@ -109,11 +109,13 @@ </handlers> </root-logger> <formatter name="OPENSHIFT"> - <custom-formatter module="org.jboss.logmanager.ext" class="org.jboss.logmanager.ext.formatters.LogstashFormatter"> - <properties> - <property name="metaData" value="log-handler=CONSOLE"/> - </properties> - </custom-formatter> + <json-formatter> + <exception-output-type value="formatted"/> + <key-overrides timestamp="@timestamp"/> + <meta-data> + <property name="@version" value="1"/> + </meta-data> + </json-formatter> </formatter> <formatter name="COLOR-PATTERN"> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>
- is related to
-
CLOUD-2421 Clean up org.jboss.logmanager.ext handling in the EAP CD vs 7.0/7.1 images
- Verified
- links to