Miles to go 2.0 …

Arun Gupta is a technology enthusiast, avid runner, author of a best-selling book, globe trotter, a community guy, Java Champion, JavaOne Rockstar, JUG Leader, Minecraft Modder, Devoxx4Kids-er, and a Red Hatter.

Getting Started with WildFly (TechTip #1)

Wildfly_logo

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  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
    17:01:47,548 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
    17:01:47,548 INFO  [org.jboss.as] (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:

    tt1-wildfly-welcome

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] BUILD SUCCESS
[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!

Tags: ,

25 Responses to “Getting Started with WildFly (TechTip #1)”

  1. with:
    mvn clean install -Dmaven.test.skip=true

    [INFO] ————————————————————————
    [INFO] BUILD SUCCESS
    [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. […] ← Getting Started with WildFly (TechTip #1) […]

  4. […] samples work on GlassFish 4 and some need some further research. I’ve started trying them on WildFly Beta 1 as well. If the samples don’t work or you’d like to see an additional sample, please […]

  5. […] Beta 1 has been available for some time now. Tech Tip #1 shows you how to get started with it. Have you tried it […]

  6. […] were created using GlassFish and work on WildFly Beta2 Snapshot (build your self as explained in Tech Tip #1) as well. This session should be available on parleys as […]

  7. […] samples and enjoyed the interaction with the attendees. I used a mix of WildFly 8 beta 2 snapshot (get started now) and GlassFish 4 to run different samples. The walkthrough included the following […]

  8. Pietro Aragona says:

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

    [INFO] ————————————————————————
    [INFO] BUILD SUCCESS
    [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. […] TCK for Java EE 7 compliance. Make sure to try your applications on WildFly and report any bugs. Tech Tip #1 shows how to get […]

  10. […] Tech Tip #1 shows you how to get started with WildFly. github.com/arun-gupta/javaee7-samples provide a comprehensive set of Java EE 7 samples that run on WildFly. And if you are interested in creating tests for these samples, follow the steps in Devoxx 2013 Hackergarten and send a pull request. […]

  11. […] a new server…”Select “WildFly” and click on “Next>”. Use Tech Tip #1 to install WildFly locally on your machine. Specify the WildFly location on next […]

  12. […] or build WildFly following Tech Tip #1. Click on “Browse…” next to “Server Location…” and select the […]

  13. […] wildfly-8.0.0.CR1.zip or associated source code and build it yourself. Use Tech Tip #1 to get […]

  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. :)

    TIA,
    Carl

  15. […] up a WildFly instance as explained in Tech Tip #1. Deploy your application to this WildFly instance […]

  16. arungupta says:

    Carl,

    I’ll try something and let you know. Can you please file an issue at https://github.com/javaee-samples/javaee7-samples ?

  17. […] Download now (zip) and get started! […]

  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:

    adminhp,

    Can you post your log to WildFly forums at https://community.jboss.org/en/wildfly ?

    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 *


six − 6 =

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>