PQ66067: WAS 4.0.4 AFFINITYCOOKIE TAG IS MISSING IN PLUGIN-CONFIG.XML WHEN FILESERVING IS ENABLED | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description In WAS 4.0.4 "plugin-cfg.xml"has "AffinityCookie"Tag. . <UriGroup Name="KENTHINKPAD_sampleApp/default_app_URIs"> /> <Uri AffinityCookie="JSESSIONID" Name="/servlet/snoop/*" /> <Uri AffinityCookie="JSESSIONID" Name="/servlet/snoop2/*" /> </UriGroup> . When fileServingEnabled="true" plugin is not generating the AffinityCookie. <UriGroup Name="KENTHINKPAD_sampleApp/examples_URIs"> <Uri Name="/webapp/examples/*" /> </UriGroup> . Here we expect <UriGroup Name="KENTHINKPAD_sampleApp/examples_URIs"> <Uri AffinityCookie="JSESSIONID" Name="/webapp/examples/*" /> </UriGroup> .Local fix Manually editing plugin-cfg.xml to include "AffinityCookie"Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of 4.0.4 * * with apps reliant on the use of session * * affinity. * **************************************************************** * PROBLEM DESCRIPTION: When using SimpleFileServlet, session * * affinity does not work properly. * **************************************************************** * RECOMMENDATION: * **************************************************************** Suppose 3 vertical clones are present in a topology. Next, a session is created when a JSP is loaded from the 1st clone. In a properly running, session affinity abiding system, all subsequent requests for pages participating in the session should come from the 1st clone. However, this is not the case if the next request is made for an HTML page served through SimpleFileServlet. The request made after the HTML page is served will choose the next available clone, not necessarily the 1st clone which served the first JSP and created the session.Problem conclusion The AffinityCookie name will be added to the SimpleFileServlet URI in plugin-cfg.xml after the plugin is regenerated.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 #: PQ66067
IBM Group: Software Group
Modified date: Sep 25, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.