|
Problem |
Installation of maintenance packs to the WebSphere®
Application Server instance, base version 5.0 or base version 6.0, in IBM®
Rational® Application Developer version 6.0 fails with errors that state
that files are in use and cannot be updated. |
|
Cause |
Installation of fix packs, interim fixes, or refresh packs
to WebSphere Application Server require that the Application Server and
its Java™ processes be stopped prior to upgrade. When running an
installation upgrade to the WebSphere Application Server instance in
Rational Application Developer version 6.0, the upgrade can fail if the
Rational Agent Controller is running. The Rational Agent Controller uses
the PD.jar file within WebSphere Application Server version 6.0 instances
and uses several library files (such as DLL files) within WebSphere
Application Server version 5.0 instances.
Problem symptoms for WebSphere Application Server version 5.0
When the Rational Agent Controller is running while attempting to update
WebSphere Application Server version 6.0, the UpdateInstaller's
"updatelog.txt" file will show errors. The "updatelog.txt" file is written
to the maintenance pack's subdirectory in the application server's
"logs/update" directory. The errors will be similar to the following
message (boldface text indicates key phrases):
Failed to delete:
file:/<installation_root>/base_v6/java/jre/
lib/ext/PD.jar
Problem symptoms for WebSphere Application Server version 6.0
A similar problem will occur when attempting to update WebSphere
Application Server version 5.0 products. The most recently written files
in the application server's "logs/update" directory will contain errors
similar to the following message (boldface text indicates key phrases):
java.io.FileNotFoundException:
<installation_root>\java\jre\bin\dbgmalloc.dll (The
process cannot access the file because it is being used by
another process)
Note that this error message will be reported for several files. Also note
that this error message can occur because the application server or
another Java-based program is using the application server's java files,
so if the Agent Controller is shut down and this error still occurs,
ensure that all java processes are shut down. |
|
Solution |
Solution applicable to all versions of WebSphere
Make sure to stop WebSphere Application Server, Java processes, and the
Rational Agent Controller in Rational Application Developer version 6.0
prior to beginning the installation of fix packs, interim fixes, or
refresh packs. If the Agent Controller is set to start automatically in
the Windows Services panel, you will need to change the setting to manual
start and restart the server.
Please do not delete the UpdateInstaller until the errant maintenance pack
is completely removed, or completely installed without error.
Specifically, it is necessary to preserve the "java_tmp" or "java"
subdirectory under the UpdateInstaller while resolving this problem. If
"java_tmp" or "java" is removed from the UpdateInstaller directory, the
UpdateInstaller may attempt to use the Java SDK in the application server,
which is temporarily "broken" by this issue, thereby preventing the
UpdateInstaller from working.
Additional notes for WebSphere Application Server version 5.0
It is a good practice to uninstall the errant maintenance pack using
the UpdateInstaller prior to re-installing it.
Additional notes for WebSphere Application Server version 6.0
If an administrator encounters a maintenance installation problem because
the Agent Controller process is running, the UpdateInstaller may
subsequently report errors when attempting to remove the failed
maintenance pack. To resolve the maintenance pack uninstallation problem,
please follow the solution outlined in technote 1214631. |
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Software Development |
Rational Application Developer for WebSphere Software |
|
Multi-Platform |
v6.0 |
All Editions |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|
|