Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News Red Hat's JBoss Team Launch WildFly 8 with full Java EE 7 Support and a New Embeddable Web Server

Red Hat's JBoss Team Launch WildFly 8 with full Java EE 7 Support and a New Embeddable Web Server

This item in japanese

Red Hat's JBoss division has today announced the availability of WildFly 8, formerly know as JBoss Application Server. This release is Java EE7 certified, supporting both the Web and the Full profiles. WildFly also gains a completely new web server called Undertow, new security features, and a patching system for updates to the running system.

Undertow is a Servlet 3.1 container. It is also the server for the HTTP management interface. The new container includes support for HTTP Upgrade - Part of the HTTP/1.1 RFC - which allows an HTTP connection to be upgraded to another protocol. The most common use is to initiate a web socket connection which allows browsers and other clients to initiate a full duplex connection.

Since HTTP Upgrade allows you to multiplex several protocols over a single HTTP port, it removes the need for multiple ports and makes firewall configuration simpler. WildFly itself uses only two ports: JNDI and EJB calls are multiplexed over the undertow subsystem port 8080, and management is multiplexed over the web management port (9090).

As an example, this is what an initial EJB request looks like on the wire once the connection is established:

GET / HTTP/1.1
Upgrade: jboss-remoting
Connection: Upgrade
Sec-JbossRemoting-Key: dGhlIHNhbXBsZSBub25jZQ==

Undertow then replies to the client saying the upgrade is allowed and completed:

HTTP/1.1 101 Switching Protocols
Upgrade: jboss-remoting
Connection: Upgrade
Sec-JbossRemoting-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=

After that the socket is passed off to the WildFly EJB layer and it behaves as a normal EJB connection.

There is a small performance overhead to process this initial HTTP request, but once that is done the performance should be exactly the same, and since the number of ports you need is actually smaller the overall effect is expected to be beneficial. Jason Greene, WildFly Lead / JBoss EAP Platform Architect at Red Hat's JBoss division told InfoQ

There is some additional overhead in establishment since you need to process an HTTP request. However, Undertow's efficiency keeps this very low. After the upgrade request has been fulfilled the socket behaves exactly as it would in a non-HTTP setting, so the performance semantics are exactly the same from that point on. Since the impact is so low, we have made this the default setting. Out of the box, WildFly 8 only has 2 HTTP ports, one for management, and one for application usage. All other protocols reuse these ports.

Undertow is also designed to be used in embedded mode. There is a chained builder API that you can use to construct the server and register an HTTP handler, which processes requests in a non-blocking fashion. Here's an example from the website

public class HelloWorldServer {

    public static void main(final String[] args) {
        Undertow server = Undertow.builder()
                .addListener(8080, "localhost")
                .setHandler(new HttpHandler() {
                    public void handleRequest(final HttpServerExchange exchange) throws Exception {
                        exchange.getResponseHeaders().put(Headers.CONTENT_TYPE, "text/plain");
                        exchange.getResponseSender().send("Hello World");

Undertow also allows you to embed code based on the Servlet API, and there are some examples in GitHub.

As well as the new web server, WildFly 8 has considerable security improvements with the addition of both audit logging and a role based security model.

The audit system is designed to ensure that any operation against the management model gets recorded in the log which can be written either to a local file or a server.

WildFly ships with two access control providers - the "simple" one is equivalent to that provided in AS 7 and is very much all or nothing, whilst the Role Based Access Control model (RBAC) one allows different administrators to have different permissions (for example a monitoring role vs. an update role).

WildFly ships with 7 pre-defined RBAC roles:

  1. Monitor: Has fewest permissions. Can read configuration and current runtime state, cannot read sensitive resources or data, and cannot read the audit log and related resources.
  2. Operator: Has all the permissions of the monitor role. Additionally, can modify the runtime state - reload or shutdown a server, pause/resume a JMS destination. An operator cannot modify persistent configuration.
  3. Maintainer: All the permissions of the operator role. Can modify persistent configuration so can deploy an application, add a JMS destination and so on. The maintainer role can edit almost all configuration associated with the server and its deployments. However, the maintainer cannot read or modify sensitive information (like passwords), and cannot read or modify audit information.
  4. Deployer: Much the same as the maintainer, but is also limited to just deployment related changes. A deployer cannot alter general server configuration.
  5. Administrator: Can see and modify sensitive information such as passwords, security domain settings. However, cannot do anything with the audit log.
  6. Auditor: Has all the permissions of the monitor role. Essentially a read-only role but can view and modify settings related to the audit logging system.
  7. SuperUser: Equivalent to AS 7 administrator, and has full permissions.

RBAC data can be stored in pretty much any LDAP server including Active Directory.

WildFly also includes a new patching system originally developed for JBoss EAP. The system allows you to deploy a JBoss produced patch either remotely or locally. Deploying against a running system stages the patch but a restart is required for it to take effect.

Finally, whilst WildFly is primarily focussed on supporting Java EE it can be used for other languages and environments. For example the TorqueBox project allows Ruby on Rails to be run on the server.

You can find out more from the WildFly website and via this webinar recording. InfoQ also has a more extensive interview with Jason Greene where, amongst other things, we discuss some of the background to Undertow, the new audit logging system, and the impact of Oracle's decision to kill off commercial support for GlassFish.

Rate this Article