I don't understand how sticky sessions work with OHS with mod_wl_ohs plugin
I have the following environment :
- 1 WLS Cluster with 2 nodes, configured in active-active mode
- 1 Java application deployed in that cluster that produce a classic JSESSIONID session cookie to identify the session
- 2 OHS in front of this, each one targeting the cluster like this :
For some technical reason I need to have sticky session based on that JSESSIONID but I can't figure out how to setup OHS to handle the request in a sticky session mode on JSESSIONID
I've read that sticky session is active by default but what happens if my session cookie is not called JSESSIONID ? And what happens if I don't want to use sticky session for one location ?
Thanks for your help.
mod_wl_ohs is similar to the mod_wl plug-in, which you can use to proxy requests from Apache HTTP Server to Oracle WebLogic server.
Please see the below doc : http://docs.oracle.com/cd/E23943_01/web.1111/e10144/under_mods.htm#BABGCGHJ
Section : 3.11 mod_wl_ohs
And as per the below Doc :
Section : Failover, Cookies, and HTTP Sessions
Session Stickness is default property for Proxy Plug-in.
Have you tried using the parameter : WLCookieName
Please check the below link for details :
Edited by: sandeep_singh on Oct 9, 2012 6:09 PM
it answers to my question.
So to summarize :
- OHS manages sticky session by default (initialy thrugh round-robin) if a cluster is targeted
- in OHS WLCookieName param let redefine the name of the Session ID if needed
- Session replication can be disabled from weblogic.xml in the webapp
- If session replication is not required, it is recommended to not create a WLS cluster in order to avoid useless multicast traffic as well as turn off session replication automatically