-
Bug
-
Resolution: Done
-
Blocker
-
None
-
EAP-XP-3.0.0.GA
-
None
-
False
-
False
-
-
-
-
-
-
+
-
Workaround Exists
-
-
There's a hard-coded check in SetupManagerAction.java that expects a 7.3 CP version.
Trying to use the manager with EAP 7.4.1 end with:
INFO: WFLYSRV0025: JBoss EAP 7.4.1.GA (WildFly Core 15.0.4.Final-redhat-00001) started in 5310ms - Started 60 of 83 services (32 services are lazy, passive or on-demand) Checking the server version. Checking the server cumulative patch id. [ERROR] An error happened setting up the JBoss EAP XP stream, the attempted filesystem changes will be rolled back. java.lang.IllegalStateException: The cumulative-patch-id in /core-service=patching:read-resource(recursive=true, include-runtime=true) was 'jboss-eap-7.4.1.CP'. A value of 'base' or one matching the regular expression 'jboss-eap-7\.3\.\d+\.CP' is expected in an untouched JBoss EAP server. at org.jboss.eap.util.xp.patch.stream.manager.SetupManagerAction.checkCumulativePatchId(SetupManagerAction.java:324) at org.jboss.eap.util.xp.patch.stream.manager.SetupManagerAction.install(SetupManagerAction.java:117) at org.jboss.eap.util.xp.patch.stream.manager.SetupManagerAction.doExecute(SetupManagerAction.java:99) at org.jboss.eap.util.xp.patch.stream.manager.ManagerAction.execute(ManagerAction.java:41) at org.jboss.eap.util.xp.patch.stream.manager.ManagerMain.main(ManagerMain.java:50) [INFO] Stopping external process containing embedded server. Sep 20, 2021 11:26:44 AM org.jboss.as.server.ApplicationServerService stop INFO: WFLYSRV0050: JBoss EAP 7.4.1.GA (WildFly Core 15.0.4.Final-redhat-00001) stopped in 44ms
As a workaround it would be possible to first execute the manager on top of an unpatched 7.4.0 and apply the CP patch after that.
