-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
The start command for server 2 stuck and is not finished.
The command for server 1 immediately end after server is up and running.
mvn wildfly:start -Djboss-as.home=target/server
It is finished without any issue. See the output:
11:35:26,039 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled 11:35:26,045 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly 35.0.0.Final (WildFly Core 27.0.0.Final) started in 4494ms - Started 512 of 700 services (375 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml - Minimum feature stability level: community [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.559 s [INFO] Finished at: 2025-02-20T11:35:26+01:00 [INFO] ------------------------------------------------------------------------
The start command for server 2 is stuck after start and the maven command is not finished till the server is shutdown.
mvn wildfly:start -Djboss-as.home=target/server2 -Dwildfly.port=10090 -Dwildfly.javaOpts="-Djboss.socket.binding.port-offset=100"
see the maven output:
11:55:24,903 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled 11:55:24,905 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly 35.0.0.Final (WildFly Core 27.0.0.Final) started in 2610ms - Started 509 of 700 services (375 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml - Minimum feature stability level: community
The exit status of the start command for server 2 is 1 that indicate a error. The exit status of the start command for server 1 is 0 that indicated a success.
No more useful info is logged.
- clones
-
-
- Ready for QA
-
