We are using Wildfly 8.1.0-Final in domain mode with mod-cluster.
We use a non-standard session id in a web application as follows:
...
<distributable />
<session-config>
<cookie-config>
<name>VSOPSESSIONID</name>
</cookie-config>
</session-config>
...

During testing of this we had our sticky set to JSESSIONID which caused requests to be forwarded to our 2 nodes alternatively.

In our 1st request we do:

request.getSession().setAttribute(KEY, value)

In our 2nd request we do:

request.getSession.getAttribute(KEY)

The second request always returns null.

When we remove the custom session id, the session data is avaliable.