WL_Plugin Is Ignoring Server Session Information when WebLogic Cluster Have Remote Nodes
(Doc ID 1958015.1)
Last updated on AUGUST 22, 2022
Applies to:Oracle WebLogic Server - Version 10.3.6 to 184.108.40.206.0
Information in this document applies to any platform.
HTTP Sessions are being ignored and re-initialized the sessions frequently, so loosing session information.
By analyzing HTTP Headers from WLS for the first JSESSIONID
[Fri Nov 21 18:36:10 2014] [info] [client xx.xxx.xx.xxx]
weblogic: Header from WLS:[Set-Cookie]=[JSESSIONID=JSESSIOn; path=/; HttpOnly]
Here see that there is no host information set by WLS in the Set-Cookie filed. Normally after the alpha numeric numbers there will be a ! (exclamation mark) followed by a number used to be there eg: abcdefgh!12345678.
Hence from the next request which contains the request with JSESSIONID=JSESSION; there is no way for plugin to parse the hostname in order to forward the request to the server where the session is set previously.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document