Last updated on JANUARY 17, 2017
Applies to:Oracle HTTP Server - Version 18.104.22.168.0 to 22.214.171.124.0 [Release Oracle11g]
Information in this document applies to any platform.
- Architecture is as follows:
Load Balancer -> 2 x Oracle HTTP Server (OHS) -> Weblogic Server (WLS) Cluster
- Session stickiness is lost when mod_wl_ohs is trying to forward https requests to the WLS Cluster
- Bypassing the load balancer and requesting directly to OHS shows the same behaviour
- OHS/mod_wl_ohs is routing https requests in a round-robin manner to the WLS servers at the backend
- Mod_wl_ohs is not honoring the session stickiness and hence first request goes to first JVM, second request from same client goes to second JVM, third request to first jvm, and so on.
- This is only seen for HTTPS requests. For http requests the plugin is routing request based on the JVMID received as part of the JSESSIONID cookie. But for https request it is not routing based on that.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms