In this recipe, we will learn how to check the server status. WildFly may have different status depending on its phase: starting, stopping, started, and stopped. Sometimes, just checking its status at the OS level by looking for its process might not be enough.
As the CLI is a management tool, you will need to have your WildFly instance up and running. Also for this recipe, we will rely on the default standalone configuration.
Open a terminal window and start WildFly:
$ cd $WILDFLY_HOME $ ./bin/standalone.sh ... 22:12:23,600 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.0.Beta2 (WildFly Core 1.0.0.Beta2) started in 3226ms - Started 202 of 379 services (210 services are lazy, passive or on-demand)