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

Posted on

Start Wildfly Application Server’s service in Microsoft Windows

In this article, the main focus is to start the Wildfly Application Server’s service. In this context, starting the Wildfly Application Server is in a Microsoft Windows-based operating system. So, in order to do that, the following is the actual process to achieve it :

  1. The first step is just by running and accessing the Command Prompt. Either run it as a normal user or even Administrator. The following window will appear below :

    How to Start Wildfly Application Server's service in Microsoft Windows
    How to Start Wildfly Application Server’s service in Microsoft Windows
  2. Next, just try to 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. Just type the following command according to the location in this context :

    Microsoft Windows [Version 10.0.19042.1052]
    (c) Microsoft Corporation. All rights reserved.
    
    C:\WINDOWS\system32>cd \
    
    C:\>cd wildfly-20.0.1.Final
    
    C:\wildfly-20.0.1.Final>cd bin
    
    C:\wildfly-20.0.1.Final\bin>
    
  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>standalone.bat
    

    If the process for starting the Wildfly Application Server is a success, the following display the actual log output of executing the above command :

    C:\wildfly-20.0.1.Final\bin>standalone.bat
    Calling "C:\wildfly-20.0.1.Final\bin\standalone.conf.bat"
    Setting JAVA property to "C:\jdk-14\bin\java"
    ===============================================================================
    
      JBoss Bootstrap Environment
    
      JBOSS_HOME: "C:\wildfly-20.0.1.Final"
    
      JAVA: "C:\jdk-14\bin\java"
    
      JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms1024M -Xmx1024M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman  --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"
    
    ===============================================================================
    
    21:52:43,308 INFO  [org.jboss.modules] (main) JBoss Modules version 1.10.1.Final
    21:52:45,533 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
    21:52:45,546 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
    21:52:45,726 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 20.0.1.Final (WildFly Core 12.0.3.Final) starting
    21:52:47,334 INFO  [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.12.1.Final
    21:52:50,610 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
    21:52:50,637 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 36) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
    21:52:51,023 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
    21:52:51,046 INFO  [org.xnio] (MSC service thread 1-7) XNIO version 3.8.1.Final
    21:52:51,054 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.8.1.Final
    21:52:51,181 INFO  [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.22.Final)
    21:52:51,308 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52) WFLYCLINF0001: Activating Infinispan subsystem.
    21:52:51,372 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 76) WFLYWS0002: Activating WebServices Extension
    21:52:51,365 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 61) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
    21:52:51,259 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 44) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
    21:52:51,473 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 74) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
    21:52:51,477 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 54) WFLYRS0016: RESTEasy version 3.12.1.Final
    21:52:51,478 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 66) WFLYNAM0001: Activating Naming Subsystem
    21:52:51,410 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 59) WFLYJSF0007: Activated the following JSF Implementations: [main]
    21:52:51,409 INFO  [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 64) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
    21:52:51,402 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 65) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
    21:52:51,384 INFO  [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 63) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
    21:52:51,384 INFO  [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 62) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
    21:52:51,373 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 72) WFLYSEC0002: Activating Security Subsystem
    21:52:51,561 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 44) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
    21:52:51,585 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
    21:52:51,836 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.1.3.Final starting
    21:52:51,986 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = mysql
    21:52:51,873 INFO  [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=5.0.3.Final-redhat-00005
    21:52:52,044 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0014: Creating file handler for path 'C:\wildfly-20.0.1.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
    21:52:52,160 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
    21:52:52,167 INFO  [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
    21:52:53,296 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 53) WFLYIO001: Worker 'default' has auto-configured to 16 IO threads with 128 max task threads based on your 8 available processors
    21:52:53,305 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
    21:52:53,305 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
    21:52:53,352 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.18.Final
    21:52:53,397 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
    21:52:53,402 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting
    21:52:53,454 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
    

    Finally, if the above output appear, actually it indicates and informs that the Wildfly Application Server’s service is finally start.

Leave a Reply