-
1. Re: Sticky session not maintain with httpd mod_proxy + wildfly 11
lukaszracon Apr 5, 2018 1:26 PM (in response to jatinkansagara)Double check if jsessionid has suffix that matches your JVM route.
See jboss.node.name property: High Availability Guide and question here for visualization (skip answers since you want to keep it) How to remove the $ {jboss.node.name} or instance-id in JsessionId?
-
2. Re: Sticky session not maintain with httpd mod_proxy + wildfly 11
jatinkansagara Apr 11, 2018 3:07 AM (in response to lukaszracon)Same settings also working with wildfly 8.
Can you please help to resolve this problem.
-
3. Re: Sticky session not maintain with httpd mod_proxy + wildfly 11
lukaszracon Apr 12, 2018 1:14 PM (in response to jatinkansagara)Did you check jboss.node.name and node-id?
How does your jesssion string looks like?
Does it contain ".master:instance1"?
-
4. Re: Sticky session not maintain with httpd mod_proxy + wildfly 11
jatinkansagara Apr 27, 2018 1:23 AM (in response to lukaszracon)jboss.node.name is "master:instance1".
jession looks like jsessionid.
-
5. Re: Sticky session not maintain with httpd mod_proxy + wildfly 11
pferraro Apr 27, 2018 8:11 AM (in response to jatinkansagara)Keep in mind that the session ID value reported by HttpSession.getId() will never contain the route. It is only appended when the session is encoded into urls or the JSESSIONID cookie.
jatinkansagara Is this a <distributable/> web application?
Have you tried without the ":" in the node name? I'm not 100% certain that won't be problematic.