JRun sticky sessions fail with custom cookie nameProducts affected
Issue
When using clustering in JRun, sticky sessions do not work if a custom cookie name is used instead of the default 'JSESSIONID' in jrun-web.xml.
Reason
JSESSIONID is used internally in JRun to maintain sticky sessions.
Solution
Enhancement Request 62342 has been logged to resolve this issue.
Workaround:
Do not use custom cookie names. Use the default configuration of jrun-web.xml or<cookie-name>JSESSIONID</cookie-name> instead.
Note: JSESSIONID must be in all uppercase.
Doc ID
(253e3f41)
Last updated
2006-04-26
Products affected
