APAR status
Closed as program error.
Error description
When the updateInstaller is invoked (either by updateWizard or
updateSilent), it checks for the presence of an executable java
in the java_tmp subdirectory. If it does not find that java,
then it checks to make sure JAVA_HOME is defined. If it is not
defined, then it attempts to invoke setupCmdLine to set
JAVA_HOME. If that fails, then the updateInstaller quits,
prompting the user to run setupCmdLine.
Problems can occur if no java_tmp exists and JAVA_HOME is set to
a non-WebSphere JRE. The updateInstaller script will copy that
non-WebSphere JRE into java_tmp. It then attempts to use
that JRE, which can result in a number of errors. The JRE may
produce a core dump on startup, or may throw this exception:
java.lang.NoSuchMethodError: javax.xml.parsers.SAXParser: method
getXMLReader()Lorg/xml/sax/XMLReader; not found
Currently, our solution is to:
1. Delete the updateInstaller java_tmp subdirectory
2. Source setupCmdLine. (On UNIX, executing it is insufficient.
Instead, it must be "sourced" with ". ./setupCmdLine.sh".
The dot-space-dot-slash is important.
3. Re-run the updateInstaller.
Local fix
This APAR has been opened as a result of discussions between
customer support and the development team. We believe that a
small change to the updateInstaller will help prevent this
situation from occuring in new versions of the updateInstaller.
The updateInstaller will check for the presence of the WAS_HOME
environment variable. If it is not set, then setupCmdLine.sh
was not properly sourced. In that case, the updateInstaller
will quit and instruct the user to properly source
setupCmdLine.sh.
Note that this solution will not repair bad JRE copies in
java_tmp. The workaround listed above this section still
applies to those situations. The intent of this APAR is to
prevent those situations from happening in the first place.
Problem summary
****************************************************************
* USERS AFFECTED: Users installing WebSphere Application *
* Server version 5.0 and 5.1 fixpack, ifixes *
* and cumulative fixpacks using the Update *
* Installer. *
****************************************************************
* PROBLEM DESCRIPTION: One manual step required to run the *
* Update Installer is to manually source *
* the WAS_HOME/bin/setupCmdLine.sh on *
* unix and run the *
* WAS_HOME/bin/setupCmdLine.bat on *
* Windows so that the required Update *
* Installer environment variables are *
* set. This manual step was being *
* missed resulting in undesirable *
* behaviour. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
An update has been made to the scripts that run Update
Installer to check that WAS_HOME and JAVA_HOME environment
variables are set before running Update Installer. If users
have not run(sourced) setupCmdLine.bat(sh) correctly, this
check will be a reminder. This will ensure that JAVA_HOME
is set correctly and thus the WebSphere Application Server
JDK is being used.
Problem conclusion
Now Update Installer will not run if the environment variables
it needs are not set correctly.
Temporary fix Comments
APAR information |
APAR number |
PQ86349 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-03-18 |
Closed date |
2004-05-04 |
Last modified date |
2004-05-04 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|