[
https://issues.jboss.org/browse/WFLY-4414?page=com.atlassian.jira.plugin....
]
Robert Smith commented on WFLY-4414:
------------------------------------
No we cannot. We are not on Wildfly 10, we are possibly moving to 9 in the near future.
You should be able to test it pretty easily by creating a custom named session id in your
web xml.
Non Standard SESSIONID not clustered
------------------------------------
Key: WFLY-4414
URL:
https://issues.jboss.org/browse/WFLY-4414
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 8.1.0.Final
Reporter: Robert Smith
Assignee: Radoslav Husar
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)