PQ67476: WEBSPHERE APPLICATION SERVER 4.04 AND MS IIS V5 SESSIONID COOKIEPLUGIN URI GROUP | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Websphere Application Server V4.04 MS IIS webserver V5 Customer has two nodes (two boxes) with five ServerGroups containing two clone ids The WAS IIS plugin does not always send requests (after the first request and a session has been established) back to the same clone. It appears from plugin trace that the sessionid cookie is sent with the request but plugin 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. ************************************************************* Plugin 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' .... This also fixes a separate problem where certain types of URI definitions require the plugin to internally create another URI definition in order to correctly match. As a result, if the original URI had a special affinity cookie set the new URI would not get updated with that affinity cookie. If the new URI was the one matched, the wrong affinity cookie would be used.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of the * * webserver plugins that have multiple * * affinity cookies defined within the plugin * * configuration. * **************************************************************** * PROBLEM DESCRIPTION: Even though the plugin configuration * * had multiple affinity cookies defined, * * the plugin would only look for the one * * for the last uri it had looked at. * **************************************************************** * RECOMMENDATION: * **************************************************************** The plugin would search for the wrong affinity cookie when multiple affinity cookies were defined in a plugin configuration.Problem conclusion Change the plugin so that is used the affinity cookie from the uri it matched during route determination.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ67476
IBM Group: Software Group
Modified date: Oct 29, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.