How to check if an application is running on WildFly

by

The simplest way to check the status of an application running on JBoss / WildFly is to use the CLI tool and the deployment-info command. Let’s see how to do it.

Here’s an example: supposing you have deployed the helloworld.war application, launch the CLI and connect to the server:

$ bin/jboss-cli.sh -c

Then, check the status of the helloworld.war application:

[standalone@localhost:9990 /] deployment-info --name=helloworld.war
NAME           RUNTIME-NAME   PERSISTENT ENABLED STATUS 
helloworld.war helloworld.war true       true    OK

There can be three possible states:

  1. OK: indicates that the deploy is up and running.
  2. FAILED: indicates a dependency is missing or a service could not start.
  3. STOPPED: indicates that the deployment was not enabled or was manually stopped.

Checking application status from the Web console

Another option is to use the Web Console to check the application’s status. Create a management user and connect to the Web Console ( See the following tutorial to learn more: How to manage JBoss / WildFly remotely

Once connected to the Console, head to the Deployments tab and choose the application you want to check:

check application status jboss

As you can see, the same Status code are reported in the Web console.

That’s it. We have covered two ways to check if an application is running on JBoss/WildFly. If you want to check the status of the application itself, we recommend the following article: How to check if JBoss is running?

JBoss AS 5

If you are still running JBoss AS 5, you can use the twiddle command line tool instead.

This is a two process step: at first you need to retrieve the deployment-id associated with your application:

twiddle -s localhost:1099 query jboss.web.deployment:*

jboss.web.deployment:war=invoker.war,id=1188245482
jboss.web.deployment:war=jbossmq-httpil.war,id=818328454
jboss.web.deployment:war=jmx-console.war,id=-742061087
jboss.web.deployment:war=jboss-seam-registration.war,id=209639553
jboss.web.deployment:war=jbossws-context.war,id=270573684
jboss.web.deployment:war=jboss-profiler.war,id=1640316612
jboss.web.deployment:war=jboss-seam-messages.war,id=-632397857
jboss.web.deployment:war=ROOT.war,id=1273039891
jboss.web.deployment:war=jboss-seam-numberguess.war,id=-1863357686
jboss.web.deployment:war=Gap.war,id=-1263613270
jboss.web.deployment:war=web-console.war,id=2121270277

Now feed this id to twiddle issuing a get request :

twiddle -s localhost:1099 get –noprefix “jboss.web.deployment:war=Gap.war,id=-1263613270” StateString

Started

Notice that Unix users can use the magic “expansion” facility to get this just in one step:

./twiddle.sh -s 127.0.0.1:1099 get –noprefix `./twiddle.sh -s 127.0.0.1:1099 query jboss.web.deployment:* | grep war_name` StateString