Details
Major Description
Property WILDFLY_SERVER_CONFIG in /etc/opt/rh/eap8/wildfly/eap8-standalone.conf has no effect on RHEL9. No matter what value it has, the server is always started with standalone.xml. It works fine with RHEL8.
/etc/opt/rh/eap8/wildfly/eap8-standalone.conf
# The configuration you want to run # Location of java in the JRE (the default) #JAVA_HOME=/usr/lib/jvm/jre # Use the following for location of java in the SDK # JAVA_HOME=/usr/lib/jvm/java # Make sure java is on your path #JAVAPTH="/usr/lib/jvm/jre/bin" # Location to keep the console log, the file to be searched for the server # start up message besides /var/opt/rh/eap8/log/wildfly/standalone/server.log #WILDFLY_CONSOLE_LOG=/var/opt/rh/eap8/log/wildfly/standalone/console.log # Define the script to use to start wildfly #WILDFLY_SH="/opt/rh/eap8/root/usr/share/wildfly/bin/standalone.sh" # Define server configuration to start, eg. standalone.xml #WILDFLY_SERVER_CONFIG=standalone.xml # Define where wildfly module directory is #WILDFLY_MODULEPATH="/opt/rh/eap8/root/usr/share/wildfly/modules" # The address to bind to #WILDFLY_BIND=0.0.0.0 # Additionals args to include on startup #WILDFLY_OPTS="" WILDFLY_SERVER_CONFIG=standalone-full-ha.xml
# service eap8-standalone stop Redirecting to /bin/systemctl stop eap8-standalone.service # service eap8-standalone start Redirecting to /bin/systemctl start eap8-standalone.service # tail -1 /opt/rh/eap8/root/usr/share/wildfly/standalone/log/server.log 2023-11-29 10:58:41,503 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 8.0.0.GA (WildFly Core 21.0.4.Final-redhat-00001) started in 4128ms - Started 281 of 523 services (317 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml