PQ77023: GETTING XERCES ERRORS WITH REPLACEMENT XERCES IN LIB/APP AFTER INSTALLING FIXPACK 6 (4.0.6)

 A fix is available

4.0.7: WebSphere Application Server Version 4.0 Fix Pack 7



APAR status
Closed as program error.

Error description
Configuration that included a different version of xerces
library in the lib/app directory worked correctly in WebSphere
4.0.5, but generated following stack trace after installing
fixpack 6 (4.0.6):
Starting EJB jar: Tasks
> WrappedExecption of java.lang.ClassCastException:
> org.apache.xerces.jaxp.SAXParserFactoryImpl
  at
  com.ibm.xmi.base.impl.StartLoad.makeParser(StartLoad.jav
  a:66)
  at
  com.ibm.xmi.base.impl.StartLoad.load(StartLoad.java:49)
Local fix
Unclear, since many customers find it beneficial to put
their libraries in lib/app instead of other locations
accessible to other classloaders.
.
The InfoCenter clearly recommends use of lib/app when the
JAR should be shared across all enterprise applications.
.
Other options are documented in rnclassholders.html, but
their applicability depends on customer's goals
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server 4.0 users.  *
****************************************************************
* PROBLEM DESCRIPTION: If a user deploys a different version   *
*                      of an exisitng class in the WebSphere   *
*                      lib directory to the lib/app directory  *
*                      (for example, Xerces), this could       *
*                      create a problem in the startup of the  *
*                      Admin Server.                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a user deploys a different version of an exisitng class in
the WebSphere lib directory to the lib/app directory
(for example, Xerces), this could create a problem in the
startup of the Admin Server.  The problem is due to the fact
that the classpath for lib/app is also enabled for the Admin
Server, when it should be disabled.
Problem conclusion
The code was modified so the lib/app classpath is disabled on
the Admin Server.  The user cannot manually override classes for
the admin server instance thru the lib/app classpath.
Temporary fix
Test fix provided to customer, now may proceed to
make the fix.
Comments
APAR information
APAR number PQ77023
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-07-31
Closed date 2003-08-25
Last modified date 2003-08-25

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
Runtime          

SRLS

Fix information

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 #: PQ77023
IBM Group: Software Group
Modified date: Aug 25, 2003