Getting Started with WildFly (TechTip #1)


JBoss Community hosts ~100 projects focused on integration, business rules, processes, NoSQL, cloud, mobile, polyglot, messaging, tooling, alternative development frameworks and more. WildFly (nee JBoss Application Server or JBoss AS) is undoubtedly the most popular project in this community.

This Tech Tip will show how to get started with WildFly.

  • JDK7: WildFly requires JDK 7. So if you do not have it already installed on your machine then download your platform-specific package for JDK 7 U45 and install.
  • Binary or Source Bundle: Download WildFly 8.0 Beta1 binary.You can also download associated source code and build it yourself too!
  • Operation Mode: WildFly has two modes of operation: Standalone and Domain. In Standalone mode, a single instance of WildFly server is started. WildFly Domain mode allows you to control and configure multiple instances.Standalone WildFly instance can be started as:./bin/standalone.shIt displays a message like:
    17:01:47,547 INFO  [] (Controller Boot Thread) JBAS015961: Http management interface listening on
    17:01:47,548 INFO  [] (Controller Boot Thread) JBAS015951: Admin console listening on
    17:01:47,548 INFO  [] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Beta1 "WildFly" started in 5771ms - Started 180 of 217 services (62 services are lazy, passive or on-demand)

    And now you can watch the following page at localhost:8080:


And that’s it!

Now you are running WildFly on your machine. Lets see what are the key features of WildFly 8:

  • Java EE 7 support – At this point all user facing APIs have been implemented, more on this in a subsequent blog.
  • Fast Startup: Server started in about 5 seconds.
  • Small Footprint by minimizing GC pauses and starting/stopping service on demand.
  • Modular Design by loading classes on demand using JBoss Modules. OSGi 4.2 support is available out-of-the-box.
  • Unified Configuration and Management available from polished user-friendly web console, Java and HTTP APIs, and CLI. Only three ports are exposed in beta 1 (8080 for applications and 9990 for management, and the third port 9999 will be deprecated) by multiplexing protocols.

Here are some handy useful resources to take your WildFly experience to the next level:

Want to learn more about WildFly ? Watch Introduction to WildFly webinar by Jason Greene and Stuart Douglas.

I built the source code on my machine (with no .m2 directory) and saw the following message:

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 33:49.934s
[INFO] Finished at: Wed Oct 23 18:40:08 EDT 2013
[INFO] Final Memory: 319M/836M
[INFO] ------------------------------------------------------------------------

How long it takes on your machine ?

Be Sociable, Share!
  1. with:
    mvn clean install -Dmaven.test.skip=true

    [INFO] ————————————————————————
    [INFO] ————————————————————————
    [INFO] Total time: 2:22.509s
    [INFO] Finished at: Thu Oct 24 12:28:02 SAST 2013
    [INFO] Final Memory: 362M/1412M
    [INFO] ————————————————————————

  2. Nikolaos Ballas says:

    A trick…accessing the console requires usind the add-user script under /bin.You have to be careful because this affects security realms

  3. Pingback: Java EE 7 at Luxemourg JUG and JAX London | Miles to go 2.0 …

  4. Pingback: Java EE 7 Samples (Tech Tip #2) | Miles to go 2.0 …

  5. Pingback: Java EE 7 Implementations in WildFly (Tech Tip #3) | Miles to go 2.0 …

  6. Pingback: J-Fall 2013 Report | Miles to go 2.0 …

  7. Pingback: Java EE 7 at Transylvania JUG | Miles to go 2.0 …

  8. Pietro Aragona says:

    I used “mvn clean install -Dmaven.test.skip=true” in xubuntu 13.10 32bit

    [INFO] ————————————————————————
    [INFO] ————————————————————————
    [INFO] Total time: 35:43.989s
    [INFO] Finished at: Mon Nov 18 15:58:00 CET 2013
    [INFO] Final Memory: 279M/494M
    [INFO] ————————————————————————

  9. Pingback: GlassFish Commercial is Dead, WildFly and JBoss EAP to Rescue | Miles to go 2.0 …

  10. Pingback: JBoss EAP 6 Clustering Reference Architecture | Miles to go 2.0 …

  11. Pingback: Getting Started with JBoss Tools and WildFly (Tech Tip #5) | Miles to go 2.0 …

  12. Pingback: NetBeans 8 and WildFly 8 (Tech Tip #6) | Miles to go 2.0 …

  13. Pingback: WildFly 8 CR1 is now available! | Miles to go 2.0 …

  14. Arun,
    Can you point me to a working RESTEasy/CRUD example that will run on Wildfly? I have a NetBeans created REST/EclipseLink app which runs on Glassfish and I am making progress getting it running on Wildfly with links such as this, JDBC driver, etc. but it’s taking longer than I would like.

    BTW the NetBeans Wildfly plugin has helped. :)


  15. Pingback: WildFly Maven Plugin to Deploy Applications and Artifacts (Tech Tip #9) | Miles to go 2.0 …

  16. arungupta says:


    I’ll try something and let you know. Can you please file an issue at ?

  17. Pingback: WildFly 8 is now available! | Miles to go 2.0 …

  18. adminhp says:

    Wildfly 8 final installed on Windows 2012 R2 server core OS. Service installed and starts fine using service.bat. However cannot stop service using service stop or windows service.
    service stop command shows the following error:
    Using the X86-64bit version of prunsrv
    ERROR: Failed to load service configuration

    Debug level log reveals the following:

    [2014-03-13 17:12:24] [info] ( prunsrv.c:687 ) [ 1792] Stopping service ‘Wildfly’ …
    [2014-03-13 17:12:24] [debug] ( prunsrv.c:844 ) [ 2068] reportServiceStatusE: 3, 0, 3000, 0
    [2014-03-13 17:12:24] [info] ( prunsrv.c:943 ) [ 2000] Stopping service…
    [2014-03-13 17:12:24] [debug] ( prunsrv.c:1057) [ 2000] Waiting for stop worker to finish…
    [2014-03-13 17:12:28] [error] ( prunsrv.c:708 ) [ 1792] Failed to stop ‘Wildfly’ service
    [2014-03-13 17:12:28] [error] ( prunsrv.c:708 ) [ 1792] The data area passed to a system call is too small.
    [2014-03-13 17:12:28] [info] ( prunsrv.c:716 ) [ 1792] Stop service finished.
    [2014-03-13 17:12:28] [error] ( prunsrv.c:1755) [ 1792] Commons Daemon procrun failed with exit value: 6 (Failed to stop service)
    [2014-03-13 17:12:28] [error] ( prunsrv.c:1755) [ 1792] The data area passed to a system call is too small.
    [2014-03-13 17:12:32] [debug] (rprocess.c:122 ) [ 2504] Child process exit code 0
    [2014-03-13 17:12:32] [debug] ( prunsrv.c:1059) [ 2000] Stop worker finished.
    [2014-03-13 17:12:32] [debug] ( prunsrv.c:844 ) [ 2000] reportServiceStatusE: 3, 0, 300000, 0
    [2014-03-13 17:12:32] [debug] ( prunsrv.c:1093) [ 2000] Waiting for worker to die naturally…

    Any pointers for resolving this is greatly appreciated. Thanks

  19. arungupta says:


    Can you post your log to WildFly forums at ?

    I don’t have a Windows 2012 server to verify.

  20. adminhp says:

    will do, thanks Arun.

  21. Mohan Potturi says:

    This happens on Win 2008 server as well.

  22. Mohan Potturi says:

    Forgot to mention that it works just fine on 32 bit systems. The problem seem to be with the 64 bit systems.

Leave a Reply

Your email address will not be published. Required fields are marked *

five − 4 =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>