Last updated on JANUARY 04, 2015
Applies to:Oracle WebLogic Server - Version 10.3.6 to 220.127.116.11.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=MY4rJvvhwNJfvdjlJdYyJcx4q40QgkLv77dZGWbyFkKjTQNbTG1F; path=/; HttpOnly]
Here we can 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=MY4rJvvhwNJfvdjlJdYyJcx4q40QgkLv77dZGWbyFkKjTQNbTG1F; 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms