PQ74218: plugin regen does not work.identified that the parsing of plugin-cfg.xml is failing

 A fix is available

5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error description
Environment:
A DMgr server installed with WAS/ND 5.0.1 and having a cell with
two
nodes and three clusters.

Problem Description:
On a DMgr server with a cell having two nodes and three
clusters, PTF1
was installed on the DMgr server to bring it up to version
5.0.1. After
the PTF is successfully installed, genplugincfg throws a
PluginConfigException. Plugin generation works fine before the
PTF is
installed. Nothing in the cell configuration changed before or
after
the PTF was applied.
A debug trace of genplugincfg yields the following output...
>genplugincfg -debug yes
IBM WebSphere Application Server, Release 5.0
WebSphere Plugin Configuration Generator
Copyright IBM Corp., 1997-2002
PLGC0012I: Generating server plugin configuration file using the
cluster definitions in cell VDCTST050Network.
================================================================
======
PLGC0032E: Exception caught while generating plugin
configuration:
PLGC0028E: Exception while reading deployed applications for
server
Trade3_vdcts
t025.
com.ibm.websphere.plugincfg.exception.PluginConfigException:
PLGC0028E:
Local fix
Exception while reading deployed applications for server
Trade3_vdctst025.
        at
com.ibm.websphere.plugincfg.generator.ConfigurationParser.
getDeployed


 Problem Summary The problem is that the plugin regen
 does not seem to work.identified that the parsing of
 plugin-cfg.xml is failing.
LOCAL FIX:
 This problem has been reported internally (defect 162628). When
trade is installed, "UseMetaDatafromBinary" is set to True.
When you try to regen the plugin with the above param set to
true, the plugin fails to gen.  The work around is to set
"UseMetaDatafromBinary" to  False.
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server 5.0.1       *
*                 users.                                       *
****************************************************************
* PROBLEM DESCRIPTION: The following exceptions occur when     *
*                      generating the plugin config file:      *
*                                                              *
*                      PLGC0032E: Exception caught while       *
*                      generating plugin configuration:        *
*                                                              *
*                      PLGC0028E: Exception while reading      *
*                      deployed applications for server        *
*                      Trade3Server                            *
*                                                              *
*                      PLGC0034I: Root exception:              *
*                                                              *
*                      PLGC0029E: Exception reading EAR        *
*                      file D:\WebSphere\AppServer             *
*                      /installedApps/WSPINetwork              *
*                      /trade3_s0245.03.ear.                   *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the setting UseMetaDataFromBinaries is enabled, plugin
generator was looking for the EAR file in the application
server install directory.  This resulted in the plugin
exception since the application didn't exist in that location.
Problem conclusion
Plugin generator is changed to ignore the flag
"UseMetaDataFromBinaries" when it is running on the
deployment manager box. The flag is used only on the
machines where Application Server is installed.
Temporary fix
Plugin generator is changed to ignore the flag
"UseMetaDataFromBinaries" when it is running on the
deployment manager box. The flag is used only on the
machines where Application Server is installed.
Comments
APAR information
APAR number PQ74218
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-05-15
Closed date 2003-06-10
Last modified date 2003-06-10

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
Plugin          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ74218
IBM Group: Software Group
Modified date: Jun 10, 2003