Details
-
Bug
-
Resolution: Not a Bug
-
Blocker
-
None
-
7.3.5.GA, 7.3.5.CR1
-
None
-
None
-
False
-
False
-
Undefined
-
- Run server with attached configuration
- Reload server
Description
After modification configuration file server can start but only for the first time. After reboot, server can't start. Next problem is that server can't start with older configuration either.
It has been added value
decay="2.0"
for modcluster (dynamic-load-provider).
After reboot server start with log:
./standalone.sh -c standalone-full-ha-new.xml ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/Data/Prace/jboss-eap-7.3 JAVA: java JAVA_OPTS: -server -Xlog:gc*:file="/home/Data/Prace/jboss-eap-7.3/standalone/log/gc.log":time,uptimemillis:filecount=5,filesize=3M -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED =========================================================================
And that's all.
Then when I try run server with standalone.xml configuration (without any changes)
I saw:
./standalone.sh -c standalone.xml ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/Data/Prace/jboss-eap-7.3 JAVA: java JAVA_OPTS: -server -Xlog:gc*:file="/home/Data/Prace/jboss-eap-7.3/standalone/log/gc.log":time,uptimemillis:filecount=5,filesize=3M -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED ========================================================================= 13:22:26,397 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory /home/Data/Prace/jboss-eap-7.3/standalone/deployments 13:22:26,461 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443 13:22:26,510 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.3.0.Final-redhat-00001 (Apache CXF 3.3.7.redhat-00001) 13:22:26,627 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 13:22:26,630 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.3.5.GA (WildFly Core 10.1.17.Final-redhat-00001) started in 2699ms - Started 306 of 560 services (355 services are lazy, passive or on-demand) 13:22:26,631 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 13:22:26,631 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
Attachments
Issue Links
- is incorporated by
-
JBEAP-20493 Introduce a mechanism for testing property resolvability
-
- Resolved
-
- relates to
-
-
- Resolved
-
