How to Stop Wildfly Application Server’s service in Microsoft Windows

By Posted on

Stop Wildfly Application Server’s service in Microsoft Windows

In this article, the focus is about how to stop the Wildfly Application Server’s service. Stopping the Wildfly Application Server from a Microsoft Windows-based operating system. So, in order to do that, the following is the actual process to achieve it :

  1. First of all, just run and access the Command Prompt. Either run it as a normal user or even Administrator. The following window will appear below :

    How to Stop Wildfly Application Server’s service in Microsoft Windows

  2. Access the folder of the binary file of the Wildfly Application Server location. In this context, it exist in C:\wildfly-20.0.1.Final. This article is using Wildfly 20.0.1. Final version.

  3. After accessing the folder, just type and execute the following command in the command prompt as follows : 

      
 C:\wildfly-20.0.1.Final\bin>jboss-cli.bat --connect --controller=localhost:9990 --command=:shutdown
{
    "outcome" => "success",
    "result" => undefined
}
Press any key to continue . . .
C:\wildfly-20.0.1.Final\bin>

    On the other hand, the Wildfly Application Server’s process which is running maybe in another command prompt windows running the ‘startup.bat’ file will suddenly presenting the following output : 

    14:28:24,600 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host default-host stopping
14:28:24,609 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 127) WFLYCLINF0003: Stopped client-mappings cache from ejb container
14:28:24,611 INFO  [org.infinispan.manager.DefaultCacheManager] (MSC service thread 1-4) Stopping cache manager null on null
14:28:24,624 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
14:28:24,625 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2
14:28:24,629 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTP listener default suspending
14:28:24,630 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTPS listener https suspending
14:28:24,632 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
14:28:24,633 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443
14:28:24,636 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0004: Undertow 2.1.3.Final stopping
14:28:32,392 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment admin-starter.war (runtime-name: admin-starter.war) in 8529ms
14:28:32,400 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Full 20.0.1.Final (WildFly Core 12.0.3.Final) stopped in 8539ms
Press any key to continue . . .
C:\wildfly-20.0.1.Final\bin>

    Actually, the above output indicating and informing that the Wildfly Application Server’s service is finally stop.

Leave a Reply