Sharing HTTPSession between Web applications in an EAR

One of the new features of WildFly 9 is the ability to share the HTTP Session between applications which are part of the same Enterprise Archive. (This feature is described in )

Actually the main advantage of this feature is to facilitate the migration of application running on Websphere and Oracle WebLogic which have this feature. Let’s see an example application which consists of two Web applications: webapp1 and webapp2, bundled into one EAR archive:

wildfly 9 tutorial

As simple test, both our webapplications will include an index.jsp page which adds one random attribute to the session and dumps the content of the HttpSession:

session.setAttribute(java.util.UUID.randomUUID().toString(), new java.util.Date().toString());

java.util.Enumeration enames = session.getAttributeNames();
while (enames.hasMoreElements()) {
   String key = (String) enames.nextElement();
   String value = "" + session.getAttribute(key);
   out.println(key + " - " + value); 


HttpSession sharing is not enabled by default, we need to include a jboss-all.xml file in the META-INF folder of the EAR file, including a shared-session-config stanza within it:

<jboss umlns="urn:jboss:1.0">
    <shared-session-config xmlns="urn:jboss:shared-session-config:1.0">

Now if you try to switch from one Web application to another you will see that the HttpSession is correctly mantained across the two Web applications. 

Thanks to Stuart Douglas for sharing some helpful insights on this feature!