Did You Know?
Donate to TecMint

LFCS - Linux Foundation Certified SysAdmin - Exam Preparation Guide

WildFly – A New Improved JBoss Application Server for Linux

Download Your Free eBooks NOW - 10 Free Linux eBooks for Administrators

As we all know that JBoss AS has been renamed to WildFly. A lots of new features has been added and lots of has been upgraded. Finally WildFly 8.0.0 Final has been released on Feb 11.2014. WildFly Project Lead Jason Greene announced the same.

Install WildFly in Linux

WildFly 8 JBoss Application Server

WildFly 8 is Red Hat‘s Java EE 7 compliant open source application server. The Main features are as below:

Java EE 7 Compatibility

The biggest change in this is that now WildFly 8 is official Java EE7 Certified.

High Performance Web Server

Undertow is new high performance web server written in Java. Now this has been implemented in WildFly 8. This is really designed for high throughput and scalability and can handle millions of connections. Undertow’s lifecycle is completely controlled by the embedding application. This is extremely lightweight with core jar having size of 1MB and embedded server using less than 4MB of heap space. This is really great.

3Port Reduction

Since it is using Undertow which support for Upgrading HTTP, which will allow multiple protocols to be multiplexed over single HTTP port. WildFly 8 has moved nearly all of its protocols to be multiplexed over two HTTP ports: one is management and another one is application port. This is really a big change and benefit to cloud providers (such as OpenShift) who run hundreds to thousands of instances on a single server. In total, it has two default ports for configuration and they are 9990 (Web Administration Console) and 8080 (Application Console).

Management Role Based Access Control & Auditing

This is the new and interesting thing implemented in WildFly 8. By using this we can create different users and can assign those one to different roles as per requirements. I’ll show you later with screen shots.

Logging

The management API now supports the ability to list and view the available log files on a server. Now, we have attribute called “add-logging-api-dependencies” available for any kind of deployments in which we want to skip container logging. This will disable the adding of the implicit server logging dependencies. We have another option i.e. we can use a jboss-deployment-structure.xml to exclude the logging subsystem. Using this, it will help to stop the logging subsystem from going through any deployment.

We can also make use of another parameter i.e. use-deployment-logging-config for enabling/disabling processing of logging configuration files within a deployment.

Note: System Property that we were using for disabling per logging has been deprecated from this version.

Clustering

Again Big change is one clustering. All Features related to Clustering support had been changed in WildFly 8 and these includes as below:

  1. Distributed web session has been optimized for it with new Java Based Web Server i.e. Undertow.
  2. mod_cluster support for Undertow.
  3. Optimized Distributed SSO(Single Sign-On) capabilities and support for Undertow.
  4. New/optimized distributed @Stateful EJB caching implementation.
  5. WildFly 8 added some new public clustering API.
  6. For creating singleton services it provides new public APIs.
CLI Improvements

CLI Configuration has also been improved. You know All admin love to work on CLI ;). So, now we can create alias for particular server and then can use that alias whenever want to connect to that server using connect command.

There are still lots of enhancements and updates done in WildFly 8. You can check all these at:

  1. http://wildfly.org/news/2014/02/11/WildFly8-Final-Released/

Installation of WildFly 8 in Linux

Before moving ahead with Installation make sure that you have Java EE 7 installed on your system. WildFly 8 will not work with previous revisions. Please follow the below guide to install Java EE 7 in the Linux systems.

  1. Install JDK/JRE 7u25 in Linux

Step 1: Downloading WildFly 8

Use the following link to download the latest WildFly zip file.

  1. http://download.jboss.org/wildfly/8.0.0.Final/wildfly-8.0.0.Final.zip

You may also use ‘wget‘ command to download directly on the command line.

[root@tecmint]# wget http://download.jboss.org/wildfly/8.0.0.Final/wildfly-8.0.0.Final.zip

Copy zip file to any preferred location (e.g. ‘/data/‘ in my case) and extract using ‘unzip’ command.

[root@tecmint]# cp wildfly-8.0.0.Final.zip /data/
[root@tecmint]# cd /data/
[root@tecmint data]# unzip wildfly-8.0.0.Final.zip

Step 2: Setting Environment Variables

Now set some environment variables. You can set these on system wise or within your configuration files. Here I am setting within configuration files standalone.sh and standalone.conf in ‘bin‘ folder.

[root@tecmint data]# cd wildfly-8.0.0.Final
[root@tecmint data]# cd bin/

Add these two following lines to standlone.sh/standlone.conf files. Please specify your WildFly installation location and Java Home location.

JBOSS_HOME=”/data/wildfly-8.0.0.Final”
JAVA_HOME=”/data/java/jre7/bin/java”

Note: For whole system wide, you can set it under ‘/etc/profile‘ file.

Step 3: Starting WildFly 8

Now start server i.e. for standalone mode use ‘standalone.sh‘ and for domain mode use ‘domain.sh‘.

[root@tecmint bin]# ./standalone.sh
[root@tecmint bin]# ./domain.sh

But, here I am starting in standalone mode. By default it will get start by ‘standalone.xml‘ file, But You can also start with some other configuration using ‘–server-config‘ option.

As below I am starting server with ‘standalone-full-ha.xml‘ and this file is present in “$JBOSS_HOME/standalone(profile)/configuration/”.

[root@tecmint bin]# ./standalone.sh --server-config standalone-full-ha.xml
Sample Output
Calling "/data/wildfly-8.0.0.Final/standalone/configuration/standalone.conf"
Setting JAVA property to "/data/java/jre7/bin/java"
===============================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: "/data/wildfly-8.0.0.Final"

  JAVA: "/data/java/jre7/bin/java"

  JAVA_OPTS: "-client -Dprogram.name=standalone.sh -Xms64M -Xmx512M -XX:MaxPerm
Size=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman"

===============================================================================

13:55:26,403 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
13:55:33,812 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final
13:55:35,481 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015899: WildFly 8.0.0.Final "WildFly" starting
13:55:58,646 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
...........
13:56:22,778 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
13:56:22,794 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
13:56:22,794 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final "WildFly" started in 64534ms - Started 229 of 356 services (172 services are lazy, passive or on-demand)

Step 4: Acessing WildFly 8

Now you can point your browser to ‘http://localhost:8080‘ (if using the default configured http port) which brings you to the Welcome Screen.

Wildfly Welcome Screen

Wildfly Welcome Screen

From here, you can access WildFly community documentation guides and enhanced web-based Administration Console access.

Step 5: Managing WildFly 8

WildFly 8 provides two administrative consoles for managing running instance:

    1. web-based Administration Console
    2. command-line interface

Before connecting to administration console or remotely using the command line, you will need to create a new user using the ‘add-user.sh‘ script in the bin folder.

Next, go to ‘bin‘ directory, set ‘JBOSS_HOME‘ in add-user.sh (if variable is not set on system bases) and create user as below.

[root@tecmint bin]# ./add-user.sh

Once starting the script you will be guided through the process to add a new user:

Sample Output
What type of user do you wish to add?
 a) Management User (mgmt-users.properties)
 b) Application User (application-users.properties)
(a):
Enter the details of the new user to add.
Using realm 'ManagementRealm' as discovered from the existing property files.
Username : admin
The username 'admin' is easy to guess
Are you sure you want to add user 'admin' yes/no? yes
Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file.
 - The password should not be one of the following restricted values {root, admin, administrator}
 - The password should contain at least 8 characters, 1 alphanumeric character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
 - The password should be different from the username
Password :
Re-enter Password :
What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[  ]:
About to add user 'admin' for realm 'ManagementRealm'
Is this correct yes/no? yes
Added user 'admin' to file '/data/wildfly-8.0.0.Final/standalone/configuration/mgmt-users.properties'
Added user 'admin' to file /data/wildfly-8.0.0.Final/domain/configuration/mgmt-users.properties'
Added user 'admin' with groups  to file /data/wildfly-8.0.0.Final/standalone/configuration/mgmt-groups.properties'
Added user 'admin' with groups  to file /data/wildfly-8.0.0.Final/domain/configuration/mgmt-groups.properties'
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? yes
To represent the user add the following to the server-identities definition 
Press any key to continue . . .

Now access the web-based Administration Console at ‘http://localhost:9990/console‘ and enter the new created username and password to directly access the Management Console.

WildFly Login

WildFly Login

First Screen After login.

WildFly Web Panel

WildFly Web Panel

If you prefer to handle your server from the CLI, run the ‘jboss-cli.sh‘ script from the ‘bin‘ directory that offers the same capabilities available via the web-based UI.

[root@tecmint bin]# cd bin
[root@tecmint bin]# ./jboss-cli.sh --connect
Connected to standalone controller at localhost:9999

For more information, follow the official WildFly 8 documentation at https://docs.jboss.org/author/display/WFLY8/Documentation.

Read Also : WildFly (JBoss AS) – How to Access and Manage CLI Using GUI

Kuldeep Sharma

Currently, Working in Middleware(Jboss/Apache Tomcat) And POSIX related technologies. Having more than 5 years of experience and love to do R&D on different open source tools/technologies.

Your name can also be listed here. Work as a Paid freelancer/writer at TecMint.
Download Free eBooks
Advanced Bash-Scripting Guide
Linux Bible
A Newbie's Getting Started Guide to Linux
Ubuntu Linux Toolbox: 1000+ Commands

14 Responses

  1. Thai says:

    Why do you want to install JDK/JRE 7u25 on Feb 17 2014? 7u51 was already there for a while. Or is it because WildFly uses Guava which doesn’t work with 7u51?

    • Kuldeep says:

      Hi Thai,

      WildFly 8 the First Release which is compatible with JEE 7. It’ll work with both 7u25 and 7u51. Infact, it’ll work with any release of JDK 7.

      Hope this will help you!
      Please let us know if still you have any queries.

      Thanks!
      Kuldeep

  2. hdaz says:

    Thanks for a great write-up are you planning on doing more?

    clustered version ?? are there still many ways to deploy the cluster ??

    how about good examples of deploying apps (( i.e. different ways ?? ))

    or even a short few articles on developing some basic apps ??

    Cheers
    hdaz

    • Kuldeep says:

      Hi hdaz,

      It’s really good to know that you like this.
      Yes, we are coming with more articles on WildFly-8 i.e. About Standalone, Clustered, different ways of deployment and undeployments etc.

      Stay tuned with tecmint :) !!

      Thanks!!

  3. Abhi says:

    Thanks, the article is well written and easy to understand. Hoping to see more such posts from you. keep it bro!

  4. vilbiraju says:

    Please go through the steps that i follwed and error messages..

    correct my mistakes

    Installation Steps
    ======================================================================
    mkdir /data
    250 cd /data/
    251 LS
    252 ls
    253 unzip wildfly-8.0.0.Final.zip
    254 ls
    255 cd wildfly-8.0.0.Final
    256 ls
    257 cd bin/
    258 ls
    259 find /usr -name *jdk
    260 cd /usr/lib/jvm/java-openjdk
    261 ls
    262 cd /data/wildfly-8.0.0.Final/bin/
    263 vi standalone.conf
    264 pwd
    265 vi standalone.conf //JAVA_HOME=”/usr/lib/jvm/java-openjdk”
    //JBOSS_HOME=”/data/wildfly-8.0.0.Final”
    =======================================================================
    [root@REDHAT2 bin]# java -version
    java version “1.6.0_20″
    OpenJDK Runtime Environment (IcedTea6 1.9.7) (rhel-1.39.1.9.7.el6-i386)
    OpenJDK Client VM (build 19.0-b09, mixed mode)
    =======================================================================

    266 ./standalone.sh –server-config standalone-full-ha.xml

    [root@REDHAT2 bin]# ./standalone.sh –server-config standalone-full-ha.xml
    =========================================================================
    OUTPUT
    =========================================================================
    JBoss Bootstrap Environment

    JBOSS_HOME: /data/wildfly-8.0.0.Final

    JAVA: /usr/lib/jvm/java-openjdk/bin/java

    JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

    =========================================================================

    21:53:13,426 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
    21:53:13,436 WARN [org.jboss.modules] (main) Failed to define class org.jboss.as.jmx.PluggableMBeanServerBuilder in Module “org.jboss.as.jmx:main” from local module loader @1ffc686 (finder: local module finder @142bece (roots: /data/wildfly-8.0.0.Final/modules,/data/wildfly-8.0.0.Final/modules/system/layers/base)): java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0
    at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_20]
    at java.lang.ClassLoader.defineClass(ClassLoader.java:634) [rt.jar:1.6.0_20]
    at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.Module.loadModuleClass(Module.java:548) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) [jboss-modules.jar:1.3.0.Final]
    at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:441) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:483) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:534) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:314) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:229) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:190) [rt.jar:1.6.0_20]
    at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:320) [rt.jar:1.6.0_20]
    at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:521) [rt.jar:1.6.0_20]
    at org.jboss.modules.Main.main(Main.java:449) [jboss-modules.jar:1.3.0.Final]

    Exception in thread “main” java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
    at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
    at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
    at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
    at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
    at org.jboss.modules.Module.loadModuleClass(Module.java:548)
    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189)
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
    at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
    at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
    at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:441)
    at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:483)
    at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:534)
    at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:314)
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:229)
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:190)
    at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:320)
    at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:521)
    at org.jboss.modules.Main.main(Main.java:449)

    • Kuldeep says:

      Hi vilbiraju,

      Check your java version as :
      #java -version

      It should be 7.*. The error is due to old version of java, Upgrade this to 7 and it will work. WildFly is compatible with JDK 7.*.
      Let us know, if you still have any issues.

      Thanks!
      Kuldeep

  5. Vilbi Raju says:

    Please go thrrough the installation steps and error

    Installation Steps
    ======================================================================
    mkdir /data
    cd /data/
    unzip wildfly-8.0.0.Final.zip
    cd wildfly-8.0.0.Final/bin
    yum install *openjdk* -y
    find /usr -name *jdk // to see the java path /usr/lib/jvm/java-openjdk
    vi standalone.conf
    vi standalone.conf //JAVA_HOME=”/usr/lib/jvm/java-openjdk”
    //JBOSS_HOME=”/data/wildfly-8.0.0.Final”
    Java Vesion
    =======================================================================
    [root@REDHAT2 bin]# java -version
    java version “1.6.0_20″
    OpenJDK Runtime Environment (IcedTea6 1.9.7) (rhel-1.39.1.9.7.el6-i386)
    OpenJDK Client VM (build 19.0-b09, mixed mode)
    =======================================================================
    Starting Wildfly
    ./standalone.sh –server-config standalone-full-ha.xml

    OUTPUT

    [root@REDHAT2 bin]# ./standalone.sh –server-config standalone-full-ha.xml
    =========================================================================
    OUTPUT
    =========================================================================
    JBoss Bootstrap Environment

    JBOSS_HOME: /data/wildfly-8.0.0.Final

    JAVA: /usr/lib/jvm/java-openjdk/bin/java

    JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true –

    Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

    =========================================================================

    21:53:13,426 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
    21:53:13,436 WARN [org.jboss.modules] (main) Failed to define class org.jboss.as.jmx.PluggableMBeanServerBuilder in Module

    “org.jboss.as.jmx:main” from local module loader @1ffc686 (finder: local module finder @142bece (roots: /data/wildfly-

    8.0.0.Final/modules,/data/wildfly-8.0.0.Final/modules/system/layers/base)): java.lang.UnsupportedClassVersionError:

    org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0
    at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_20]
    at java.lang.ClassLoader.defineClass(ClassLoader.java:634) [rt.jar:1.6.0_20]
    at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.Module.loadModuleClass(Module.java:548) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) [jboss-

    modules.jar:1.3.0.Final]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) [jboss-

    modules.jar:1.3.0.Final]
    at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) [jboss-modules.jar:1.3.0.Final]
    at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) [jboss-modules.jar:1.3.0.Final]
    at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:441) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:483) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:534) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:314) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:229) [rt.jar:1.6.0_20]
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:190) [rt.jar:1.6.0_20]
    at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:320) [rt.jar:1.6.0_20]
    at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:521) [rt.jar:1.6.0_20]
    at org.jboss.modules.Main.main(Main.java:449) [jboss-modules.jar:1.3.0.Final]

    Exception in thread “main” java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported

    major.minor version 51.0
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
    at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
    at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
    at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
    at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
    at org.jboss.modules.Module.loadModuleClass(Module.java:548)
    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189)
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
    at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
    at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
    at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:441)
    at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:483)
    at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:534)
    at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:314)
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:229)
    at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:190)
    at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:320)
    at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:521)
    at org.jboss.modules.Main.main(Main.java:449)

  6. khaya-mfini says:

    Hi Vilbi,

    I know it’s months after, but you may want to also change your “alternatives” on your system for java. I have written steps for you below:

    1. First install Java EE 7 on the server or pc
    1.1) Download:
    jdk-7u67-linux-i586.tar.gz (this should contain a jre on it)

    1.2) Extract to /opt

    1.3) Create a symlink called “java”
    $ cd /opt
    $ ln -s /opt/jdk1.7.0_67 java

    1.4) You should see:
    lrwxrwxrwx 1 root root 11 Aug 24 15:25 java -> jdk1.7.0_67
    drwxr-xr-x 8 uucp 143 4096 Jul 25 18:14 jdk1.7.0_67

    1.5) Make this version of java default:

    1.5.1) Edit /etc/environment and append “/opt/java/bin” to your PATH environment variable.
    Also add a JAVA_HOME that is set to “/opt/java”. Something like:

    PATH=”/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/java/bin”
    JAVA_HOME=”/opt/java”

    These will take effect next time you restart your pc.

    1.5.2) $ sudo update-alternatives –install “/usr/bin/java” “java” “/opt/java/jre/bin/java” 1
    1.5.3) $ sudo update-alternatives –config java
    1.5.4) Check if version is correct: $ java -version
    java version “1.7.0_67″
    Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
    Java HotSpot(TM) Client VM (build 24.65-b04, mixed mode)

  7. Kuldeep says:

    Hi Vilbi,

    Sorry, I didn’t noticed about your comment.
    Just, upgrade your jdk to version 7 as Wildwfly doesn’t support 6 or older.

    @khaya-mfini
    Thank you!!
    Its good to add things to alternatives. But, another thing that I would suggest is that you can Install jdk-1.7 to any specific directory and it just set your variable in standalone.conf/sh file.
    With this you can have multiple java version running on same systems and will not break running things :)..

    Thanks!!

Leave a Reply

This work is licensed under a (cc) BY-NC | TecMint uses cookies. By using our services, you comply to use of our cookies. More info: Privacy Policy.
© 2012-2014 All Rights Reserved.