|
Problem(Abstract) |
Installation of WebSphere® Application Server fix packs,
fixes and cumulative fixes will fail if all WebSphere Application Server
processes are not stopped and all files are released that might be held by
other processes or programs. |
|
|
|
Cause |
It is well documented to stop all WebSphere Application
Server processes before installing maintenance to WebSphere Application
Server. If all Application Server processes are stopped and the
installation or upgrade still fails, check to see if there are any other
processes or programs running that are using, or are connected to, an
Application Server process or file. The running process that is connected
to WebSphere Application Server can tie up a component or file and prevent
it from being updated.
Errors such as the following could occur:
WUPD0248E: Fix pack update failure:
The processing of fix pack was502_cf9_win, component prereq.jsse failed.
See the log file
install_root\logs\update\20050521_062349_was502_cf9_win_prereq.
jsse_install.log for processing details.
2005-05-21T06:23:50Z Error 16 -- File could not be deleted:
install_root\\lib\gskikm.jar |
|
Once the updateInstaller finds a process or file in use, the install will
fail. |
|
|
Resolving the
problem |
When performing maintenance or upgrades to WebSphere
Application Server, make sure the updates are performed with required user
permissions (actual root user, for UNIX®-based systems, and user with
administrator authority on Windows-based systems), all Application Server
Java™ processes are stopped, and Web server processes are stopped if the
Web server is on the same machine. Make sure the maintenance being
installed is unpacked on the machine being upgraded by a user with proper
authority to maintain file permissions and symbolic links.
If the install still fails after following the preceding requirements,
there might be another program or process running that has connected to a
WebSphere Application Server file or process that is preventing the
installation. Check to see in which file or process the Application Server
installation failed. Once identified from the installation log file,
identify the process or program holding the file open and stop it. Once
stopped, the installation should now complete successfully.
For UNIX-based systems, the command lsof should list the running
processes and the owner so they can be identified and stopped. For
Windows®-based systems, a third-party freeware program, such as Handle
V3.20, can perform a similar function. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|