PQ59146: WAS FIXPACK 2 REQUIRES THE SAMPLEAPP TO BE PRESENT IN ORDER TO COMPLETE SUCCESSFULLY | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Customer had WAS 4.0.1 installed, and had removed the SampleApp from his configuration. When he tried to install FixPack 2 (i.e., 4.0.2), the install failed. When he created the SampleApp, and tried the install again, it succeeded. . Level 2 was able to recreate the failure, and has the was40_ae_ptf_2.log from this install.Local fix Verify that the SampleApp exists before FixPack 2 is installed. If not, recreate it before installing FixPack 2.Problem summary **************************************************************** * USERS AFFECTED: Websphere Application Users applying a ptf * * level to 4.0.1 product. * **************************************************************** * PROBLEM DESCRIPTION: Websphere Application User has removed * * a jar (Increment.jar) from the samples * * subdirectory. As a result, an error * * appears when they try to apply ptf 2. * * It indicates that a fatal error has * * occured since Increment.jar could not * * be found. * **************************************************************** * RECOMMENDATION: * **************************************************************** Websphere Application User has removed a jar (Increment.jar) from the samples subdirectory. As a result, an error appears when they try to apply ptf 2. It indicates that a fatal error has occured since Increment.jar could not be found. The install does not continue even though in terms of the whole installation it really isn't a "fatal error". JDK and IHS and other upgrades do not proceed which in turn compromise the viability of the install after ptf.Problem conclusion In the 4.0.3 ptf, a number of changes have been made. When a user comes through the support process, we can direct them that the missing Increment.jar is a benign error and to re-run the ptf without reinstalling the Application Server or if silently, set IGNORE_WAS to true. Another possible approach would have been to distinguish in the extractor files that are "benign" or not. However.. this went against what the designers had in mind for the ptf.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ59146
IBM Group: Software Group
Modified date: Jan 10, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.