Installing Wildfly Java Application Server

Posted on

Operating System version            : Ubuntu Xenial Xerus (16.04)

Wildfly version                             : 10

Installing Wildfly Java Application Server in Ubuntu Xenial Xerus (16.04)

In this article, we are going to specify the installation of one type of Application Server recognized for running systems or applications which is being developed with Java Programming language. The Applicatoin Server itself is called Wildfly and the latest stable version when this article is being posted at 6th May 2016 is Wildfly 10.

Wildfly is an Application Server released as an open source software and it is developed by certain community of users.

The process of the installation of Wildfly is quite simple. It can be explained in the following steps as follows :

  1. Download the Wildfly installer in the following link. We can download it using all kinds of download utility, for an example wget or any other download utility  available depends on the operating system used.
  1. After downloading the Wildfly file installer , extract the compressed file installer as follows :
unzip []
username@hostname:~/java/appserver$ unzip
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-cli_1_3.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-config_1_0.xsd  
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-config_1_5.xsd  
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-datasources_1_1.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-datasources_1_2.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-ejb3_1_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-ejb3_1_1.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-ejb3_1_5.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-infinispan_1_1.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-infinispan_1_4.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-infinispan_4_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-jca_1_1.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-jgroups_1_1.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-jmx_1_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-jmx_1_2.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-jpa_1_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-jsr77_1_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-logging_1_3.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-logging_2_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-messaging_1_1.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-messaging_2_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/web-fragment_3_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/web-fragment_3_1.xsd
inflating: wildfly-10.0.0.Final/docs/schema/web-partialresponse_2_2.xsd
inflating: wildfly-10.0.0.Final/docs/schema/wildfly-batch-jberet_1_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/wildfly-batch_1_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/wildfly-config_3_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/wildfly-remoting_3_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/javaee_7.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-cli_1_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-cli_1_2.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-cmp_1_0.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-config_1_1.xsd
inflating: wildfly-10.0.0.Final/docs/schema/jboss-as-config_1_6.xsd
inflating: wildfly-10.0.0.Final/modules/system/layers/base/org/wildfly/extension/clustering/singleton/main/wildfly-clustering-singleton-extension-10.0.0.Final.jar
inflating: wildfly-10.0.0.Final/modules/system/layers/base/org/wildfly/extension/mod_cluster/main/module.xml
inflating: wildfly-10.0.0.Final/modules/system/layers/base/org/wildfly/extension/picketlink/main/module.xml
inflating: wildfly-10.0.0.Final/modules/system/layers/base/org/wildfly/extension/picketlink/main/wildfly-picketlink-10.0.0.Final.jar
inflating: wildfly-10.0.0.Final/modules/system/layers/base/org/wildfly/security/manager/main/module.xml
inflating: wildfly-10.0.0.Final/modules/system/layers/base/org/yaml/snakeyaml/main/module.xml
inflating: wildfly-10.0.0.Final/modules/system/layers/base/org/yaml/snakeyaml/main/snakeyaml-1.15.jar
username@hostname:~ $
  1. To be able to execute it, we can use the following command :
sh -b=

The command sh is a command name of the Bourne Shell, it is the standard command language interpreter of UNIX and many UNIX-like operating systems, including Linux operating systems. It is used in the above context to interpret and execute in order to run Wildfly Application Server.

The additional parameter -b is a parameter which is used to bind the server on specific address, in this context is the Wildfly Application Server. And since the value of its parameter is, it will bind on all of network interfaces exists in the server itself.


username@hostname:~/java/appserver/wildfly-10.0.0.Final/bin$ sh -b=


JBoss Bootstrap Environment
JBOSS_HOME: /home/username/java/appserver/wildfly-10.0.0.Final
JAVA: /home/username/java/jdk/jdk1.8.0_05/bin/java
JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true


16:48:21,887 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
16:48:22,336 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
16:48:22,477 INFO  [] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
16:48:24,934 INFO  [] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
16:48:24,992 INFO  [org.xnio] (MSC service thread 1-4) XNIO version 3.3.4.Final
16:48:25,041 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.4.Final
16:48:25,133 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.18.Final
16:48:25,339 INFO  [] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
16:48:25,346 INFO  [] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
16:48:25,481 WARN  [] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
16:48:25,501 INFO  [] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
16:48:25,503 INFO  [] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
16:48:25,538 INFO  [] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
16:48:25,548 INFO  [] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
16:48:25,604 INFO  [] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
16:48:25,678 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 1.3.15.Final starting
16:48:25,679 INFO  [] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final
16:48:25,679 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting
16:48:25,721 INFO  [] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:48:25,861 INFO  [] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2
16:48:25,909 INFO  [] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
16:48:25,984 INFO  [] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
16:48:26,478 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path '/home/username/java/appserver/wildfly-10.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
16:48:26,562 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0012: Started server default-server.
16:48:26,565 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
16:48:26,775 INFO  [] (MSC service thread 1-8) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
16:48:26,783 INFO  [] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
16:48:26,961 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on
16:48:27,487 INFO  [] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
16:48:27,883 INFO  [] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "EJBCalculator.jar" (runtime-name: "EJBCalculator.jar")
16:48:27,936 INFO  [] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory /home/username/java/appserver/wildfly-10.0.0.Final/standalone/deployments
16:48:28,472 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
16:48:28,469 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
16:48:28,465 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
16:48:28,729 INFO  [] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
16:48:29,128 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment EJBCalculator.jar
16:48:29,336 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.2.3.Final
16:48:29,567 INFO  [] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'EJBCalculatorAdd' in deployment unit 'deployment "EJBCalculator.jar"' are as follows:


16:48:29,871 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Starting Services for CDI deployment: EJBCalculator.jar
16:48:29,867 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:48:29,885 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:48:29,888 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:48:29,889 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 58) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
16:48:30,008 INFO  [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 2.3.2 (Final)
16:48:30,124 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Starting weld service for deployment EJBCalculator.jar
16:48:31,113 INFO  [] (ServerService Thread Pool -- 59) WFLYCLINF0002: Started client-mappings cache from ejb container
16:48:32,414 INFO  [] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "EJBCalculator.jar" (runtime-name : "EJBCalculator.jar")
16:48:32,695 INFO  [] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on
16:48:32,699 INFO  [] (Controller Boot Thread) WFLYSRV0051: Admin console listening on
16:48:32,700 INFO  [] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 11463ms - Started 366 of 635 services (379 services are lazy, passive or on-demand)
  1. When the process is successfully executed, we can access the following URL address to prove that the Wildfly Application has already started in your browser :

The browser will then display the following page :


One thought on “Installing Wildfly Java Application Server

Leave a Reply