PQ67476; 4.0.2, 4.0.3, 4.0.4: Plug-in session
affinity problem with cookies
Downloadable files
Abstract
Session Affinity would not work when the user had multiple
affinity cookies for the various applications they had installed.
Download Description
USERS AFFECTED:
WebSphere® Application Server users of the Web server plug-ins that have
multiple affinity cookies defined within the plug-in configuration.
Microsoft® IIS Web server V5.0 customer has two nodes, each on a separate
host, with five ServerGroups containing two clone ids.
PROBLEM DESCRIPTION: Even though the plug-in configuration had multiple
affinity cookies defined, the plug-in would only look for the one for the
last URI it had looked at. The IIS plug-in does not always send requests,
after the first request and a session has been established, back to the
same clone. It appears from plug-in trace that the sessionid cookie is
sent with the request but plug-in logic looks for a different cookie name
from a different URI/Server Group.
Should see the request coming in for AgentWebSite/dwaTest.jsp which gets
found in URI group AgentWebSite/AgentWebSite_URIs however when it tries to
parse the session id cookie for the clone name, it thinks the sessionid
name is JSESSIONIDCF which is actually from a different URI group. It
should be looking for JSESSIONIDIA as the session id cookie name.
Plug-in trace errors:
lib_htrequest: htrequestGetCookie: looking for cookie:
'JSESSIONIDCF' no cookie found GET /AgentWebSite/dwaTest.jsp
Referer: 'http://asbwww77.countrylan.net/CPLogin/login.html'
Cookie: JSESSIONIDIA
this is cookie should be looking for, not JSESSIONIDCF Plugin-cfg.xml
UriGroup Name='CountryFinancial/CountryFinancial.war_URIs'
Uri AffinityCookie='JSESSIONIDCF Name = *.jsp'
UriGroup Name='AgentWebSite/AgentWebSite_URIs'
Uri AffinityCookie='JSESSIONIDIA' Name = /AgentWebSite/*.jsp'
Session Affinity would not work when the user had multiple affinity
cookies for the various
applications they had installed.
PROBLEM CONCLUSION:
Change the plug-in so that the affinity cookie from the URI it matched
during route determination is used.