PQ68139: PLUGIN-CFG.XML FILE MUST HAVE PROPERTY NAME = CACHELIBRARY AT TOP OF THE FILE TO LOAD THE CACHE LIBRARY

 Fixes are available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
PQ86603: IBM HTTP Server V2.0.x mod_alias/mod_rewrite conflict with V5.0 plug-in



APAR status
Closed as program error.

Error description
Websphere Application Server V4.04 AE
with Websphere Commerce Suite V5.4.0.3
The customer was having problems when the Property specifying
 the WCS (Websphere Commerce Suite) cache dll was not at the
 top of the config file.
In the Websphere Application Server plugin-cfg.xml file, line
 <Property Name = "CacheLibrary">
 value = "D:\WebSphere\CommerceServer\bin\wccache.dll
   is specified.
If this line is specified before the <ServerGroup> element, it
seems to load the cache library fine.  If this line is specified
after <ServerGroup> section then the cache library is not loaded
If this line is not at the top of the plugin-cfg.xml file, the
 cache library is not loaded.
If there was a local workaround:
 Move the Property for the WCS cache dll to the top of the
  config file just below the Log element.
If this supercedes any previous APARS:
 The efixes this supercedes are listed in the README:
  WAS_Plugin_10-18-2002_4.0.x_cumulative, 
PQ67476, 
PQ67481,
  
PQ67506, 
PQ67717, 
PQ67809, 
PQ67965.
Change in behavior in WebSphere after fix is installed:
 The plugin was changed so that it will load the WCS cache
  dll correctly regardless of the position in the plugin config
  file.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Commerce Suite - Websphere         *
*                 Application Server Plugin users              *
****************************************************************
* PROBLEM DESCRIPTION: Position of cache tag in config was     *
*                      significant                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The position of the cache library config tags was significant
in the plugin-cfg.xml in a way it shouldn't have been, causing
it to fail to load the WCS cache libraries if the tag was
one of the last ones in the Config tag.
Problem conclusion
Fixed so the position doesn't matter, as long as you stay
within the confines of the dtd.
Temporary fix
I provided this fix that allows the config properties to be
anywhere in the plugin config file.  The previous problem
was the config parsing logic would add them to the last
transport defined rather than to the config list like they
were supposed to be.
Comments
APAR information
APAR number PQ68139
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-11-12
Closed date 2003-01-05
Last modified date 2003-03-21

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PQ72325

Modules/Macros
PLUGIN          

SRLS

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ68139
IBM Group: Software Group
Modified date: Mar 21, 2003