PQ68820: DOUBLE SLASHES IN EARFILE SETTING CAUSES FILENOTFOUNDEXCEPTION DURING STARTUP OF WAS 4.0.4.

 A fix is available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6



APAR status
Closed as program error.

Error description
After Upgrading to WAS PTF 4.04, unable to start the
adminserver.   Double slashes in earFile setting causes
FileNotFoundException during startup of 4.0.4.
fixpack4-installation-log shows all parts of FP4 applied OK.
  ---> FP4 installation went OK.
tracefile shows during start of AdminServer
 I ADMS0008I: Initializing WebSphere Administration server
 X ADMS0010E: Invalid EJB Jar bindings for
 com.ibm.ejs.models.base.config.applicationserver.impl.EJBModule
 (uri: nssrcm.jar)
 java.io.FileNotFoundException: nssrcm.jar
  at com.ibm.etools.commonarchive.impl.ContainerImpl.getFile
  at com.ibm.etools.commonarchive.impl.EARFileImpl.getModuleFile
  at com.ibm.etools.commonarchive.impl.EARFileImpl.getBindings
Local fix
Manually change admin.config file to remove // in the path
For example, remove the extra slash from
com.ibm.ejs.sm.adminServer.earFile=/opt//WAS/WebSphere/AppServer
/config/admin.ear
Problem summary
****************************************************************
* USERS AFFECTED: Users of WebSphere Application Server        *
*                 versions 4.0 to 4.05                         *
****************************************************************
* PROBLEM DESCRIPTION: When double separators exist in a path  *
*                      to an EAR file in a server              *
*                      configuration xml file,                 *
*                      (e.g, "D:\WebSphere\\installedApps      *
*                      \test.ear") modules in the EAR file     *
*                      fail to start. FileNotFoundExceptions   *
*                      are logged to the console.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Path resolution code in WebSphere archive loading code was
not normalizing the paths from the configuration file.
Problem conclusion
Changed the archive code to first canonicalize the paths
to remove the double separators.
Temporary fix Comments
APAR information
APAR number PQ68820
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-12-04
Closed date 2003-04-28
Last modified date 2003-04-28

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
NONE WCCM        

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 #: PQ68820
IBM Group: Software Group
Modified date: Apr 28, 2003