-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
EAP-XP-6.0.0.GA
-
None
-
False
-
-
False
-
-
-
-
-
-
-
When installing JBoss EAP XP6 from the runtime-maven-repository downloaded from the customer portal, the version reporting is broken/inconsistent, see below:
Installing the server with the below command line:
jboss-eap-installation-manager.sh install --profile eap-xp-6.0 --dir jboss-eap-xp6 --repositories eap-xp6-repo::file:<path-to>/jboss-eap-xp-6.0.0.GA-maven-repository/maven-repository,eap-8.1-repo::file:<path-to>/jboss-eap-8.1.2.GA-runtime-maven-repository/maven-repository --offline
The output during the startup is:
09:46:34,036 INFO [org.wildfly.core.installationmanager] (MSC service thread 1-2) WFLYIM0023: Installation was provisioned using the following channel versions: '[ManifestVersion{channelId='org.jboss.eap.channels:eap-xp-6.0', description='null', version='1.0.0.GA-redhat-00015'}, ManifestVersion{channelId='org.jboss.eap.channels:eap-8.1', description='EAP 8.1 Update 2.0', version='1.2.0.GA-redhat-00004'}]'
...
09:46:34,137 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 8.1 Update 2.0 (WildFly Core 27.1.2.Final-redhat-00002) started in 5868ms - Started 257 of 393 services (213 services are lazy, passive or on-demand) - Server configuration file in use: standalone-microprofile.xml
Here we have 2 issues:
- The description of the ManifestVersion logging of JBoss EAP XP is null
- The final WFLYSRV0025 startup message does not show this is a JBoss EAP XP6 server, but only shows the base server JBoss EAP 8.1 Update 2
In addition to this, the version.txt file in $JBOSS_HOME does not reflect this server to be a JBoss EAP XP6 installation. It shows only the base server version, see:
$ cat $JBOSS_HOME/version.txt Red Hat JBoss Enterprise Application Platform - Version 8.1 Update 2.0