PQ66875: AFTER RUNNING WASPOSTUPGRADE THE WRONG JRE IS USED TO START THE AES APPLICATION SERVER.

 A fix is available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as program error.

Error description
WASPostUpgrade will modify the WebSphere AES processDefinition's
"executableName" attribute in the server-cfg.xml

When WAS AES 4.0 is installed the server-cfg.xml
processDefinition's attribute "executableName" is set to use
the java that is installed with WebSphere.  For a windows
environment it would be set to "${JAVA_HOME}/bin/java".
WASPostUpgrade process will migrate this value from the
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users of WebSphere Application Server        *
*                 that migrate from WebSphere v3.x.x           *
*                 to v4.0.x Advanced Single Server Edition.    *
****************************************************************
* PROBLEM DESCRIPTION: After running WASPostUpgrade the wrong  *
*                      JRE is used to attempt to start the     *
*                      AEs Application Server and the server   *
*                      does not start.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
After running WASPostUpgrade the wrong JRE is used to attempt
to start the AEs Application Server and the server does not
start.  The problem is that the Application Server's
executable attribute "java" was mapped over from the v3.x.x
websphere_3x_backup.xml file and overwriting the Application
Server's ProcessDefinition executableName attribute
"${JAVA_HOME}/bin/java" in the v4.0.x AEs server-cfg.xml file.
Problem conclusion
The code that maps the Application Server's executable
attribute from the v3.x.x websphere_3x_backup.xml to the
Application Server's ProcessDefintion executableName attribute
in the v4.0.x server-cfg.xml file was removed.  Therefore the
executableName attribute is not being overwritten during
WASPostUpgrade.
Temporary fix Comments
APAR information
APAR number PQ66875
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-10-03
Closed date 2002-11-14
Last modified date 2002-11-14

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
MIGRATE          

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

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 #: PQ66875
IBM Group: Software Group
Modified date: Nov 14, 2002