AffinityCookie tag is missing from plugin-cfg.xml after file serving is enabled
 Technote (FAQ)
 
Problem
In WebSphere® Application Server V4.0.4, the AffinityCookie tag is missing from the plugin-cfg.xml file after file serving is enabled. When file serving is enabled, the AffinityCookie is not appended to the URI group in the plugin-cfg.xml file. This means that session affinity is not maintained.
 
Cause
This session cookie field was not editable in V4.0.0 - V4.0.3 in accordance with the Java™ 2 Enterprise Edition (J2EE) specification. Starting in V4.0.4 the session cookie name is an editable field. This allows the Java™ Virtual Machine(s) to have individual Session Databases and still maintain session affinity.
 
Solution
For V4.0.4 you must install PQ66067. V4.0.5 and subsequent releases have this fix included in the fix pack.

Download this fix from the IBM support page:
http://www-3.ibm.com/software/webservers/appserv/support/

Regenerate the plug-in on your WebSphere® Application Server machine. If the Web server is remote to the WebSphere Application Server host, you must copy the newly-generated plugin-cfg.xml to the Web server, then restart the Web server.

How to check the file serving status

The corresponding ibm-web-ext.xmi file will have this information:

fileServingEnabled="true"

Example:

$WAS_HOME\installedApps\sampleApp.ear\examples.war\WEB-INF\ibm-web-ext.xmi

Missing URIs in plugin-cfg.xml with fileServingEnabled="true"

When fileServing is enabled, WebSphere uses the context root and plugin-cfg.xml does not have an individual <Uri Name> tag for each Servlet/JSP.

 
Related information
PQ66067
How to share a session between JVMs
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Sessions and Session Management
Operating system(s): HP-UX
Software version: 4.0.7
Software edition:
Reference #: 1165844
IBM Group: Software Group
Modified date: Dec 13, 2005