[jboss-jira] [JBoss JIRA] (WFLY-4414) Non Standard SESSIONID not clustered

[Stuart Douglas (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048419#comment-13048419 ] 

Stuart Douglas commented on WFLY-4414:
--------------------------------------

What does your mod_cluster config look like? Have you configured the custom sticky session cookie name in the mod_cluster config?

> Non Standard SESSIONID not clustered
> ------------------------------------
>
>                 Key: WFLY-4414
>                 URL: https://issues.jboss.org/browse/WFLY-4414
>             Project: WildFly
>          Issue Type: Feature Request
>            Reporter: Robert Smith
>            Assignee: Jason Greene
>
> 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.3.11#6341)