|
Problem(Abstract) |
Cumulative Fixes 2, 3, 4, and 5 for WebSphere Application
Server V5.0.2 (5.0.2.2, 5.0.2.3, 5.0.2.4, 5.0.2.5) deliver changes to the
ORB component. These changes could potentially backlevel the ORB component
(delivering outdated ORB code). |
|
|
|
Cause |
The information in this article applies ONLY to
WebSphere Application Server version 5.0.2 and associated cumulative
fixes. This issue does not apply to WebSphere Application Server V5.1.
The WebSphere Application Server V5.0.2 Cumulative Fixes each deliver a
set of product code fixes to an application server or deployment manager.
These fixes are cumulative. A newer cumulative fix will contain all of the
fixes delivered by an previous cumulative fix in the same family, in
addition to new code changes delivered in that newer cumulative fix. Due
to changes in the Cumulative Fix Strategy, there is an exception to this
rule with regards to the Object Request Broker (ORB), which is closely
related to the Java SDK component at the core of the application server.
The Cumulative Fix Strategy includes two different types of cumulative
fixes: Application Server Cumulative Fixes and Java SDK cumulative fixes.
(The term "Application Server Cumulative Fixes" can also apply to
Deployment Managers and the WebSphere Application Client.) Java SDK
Cumulative Fixes were introduced several months after Application Server
Cumulative Fixes, and as a result, the Application Server Cumulative Fix
deliverables changed.
The ORB component, which is a component of the Java SDK delivered with
WebSphere Application Server, is delivered in WebSphere Application Server
V5.0.2 cumulative fixes 2, 3, 4, and 5 (version 5.0.2.2, 5.0.2.3, 5.0.2.4,
5.0.2.5). After the development of Application Server Cumulative Fix 5 was
completed, Java SDK cumulative fixes were introduced. As part of that
change, the ORB component was removed from future Application Server
Cumulative Fixes and was placed into the Java SDK cumulative fixes. The
ORB component is no longer included in Application Server Cumulative
Fixes, starting with Application Server Cumulative Fix 6 (version
5.0.2.6).
Clients currently at version 5.0.2.2 through version 5.0.2.5 should be
aware of the implications of these changes.
Starting with Application Server Cumulative Fix 6, the ORB component is no
longer updated or replaced by the Application Server Cumulative Fixes.
This means that if Application Server Cumulative Fixes 2, 3, 4, or 5 were
installed, the ORB component delivered by those Application Server
Cumulative Fixes will not be overwritten or updated by future Application
Server Cumulative Fixes. The ORB component must instead be updated via
Java SDK Cumulative Fixes.
Question: How can I tell if Application Server Cumulative Fixes 2,
3, 4, or 5 has been applied to an application server?
Answer: Look inside this directory: install_root
/properties/version/history. If a file named something similar to
"was502_cfx_platform .ptfApplied" is present, then a 5.0.2
Application Server Cumulative Fix is present. The "x" in the
cumulative fix name indicates the Cumulative Fix version applied. Note
that "platform" represents the ID of their platform (i.e., "win"
for Windows, "aix" for AIX, etc.).
One way to quickly list the cumulatives is to issue a command such as the
following, for UNIX-based systems:
ls -la install_root/properties/version/history/*cf*.ptfApplied
Question: What if Application Server Cumulative Fixes 2, 3, 4, or
5 has been applied "on top of" a Java SDK Cumulative Fix?
Answer: This could potentially "backlevel" the ORB code. In other
words, this could potentially deliver outdated ORB code on top of the
existing ORB. This is not an ideal situation, but it can be remedied by
uninstalling the latest cumulative fix installed. If each
cumulative fix is uninstalled in the reverse order from which it was
installed, the product can be restored to its earlier version state, then
newer cumulative fixes can be applied. See the Preventative Measures
section for details. |
|
|
Resolving the
problem |
Preventative Measures
In order to avoid potential problems which could occur from the delivery
of the ORB component in Application Server Cumulative Fixes 2, 3, 4, and
5, review the following suggestions:
- When possible in a new deployment, avoid installing V5.0.2 Application
Server Cumulative Fixes 2, 3, 4, and 5. Instead, install Application
Server Cumulative Fix 6 or later.
- If it is necessary to install Application Server Cumulative Fixes 2,
3, 4, or 5, then the situation can be remedied by installing the latest
available Java SDK Cumulative Fix. That cumulative fix will update the ORB
with new code.
- Uninstalling Application Server Cumulative Fixes 2, 3, 4, or 5 will
also remedy the situation, but this must be treated carefully. All
cumulative fixes must be uninstalled in the reverse order from which they
were installed. If there is doubt regarding the order of installation for
Cumulative Fixes, use the resolution suggested in Suggestion 2 instead.
Do not uninstall an early Application Server Cumulative Fix (such as
cumulative fix 5) from "underneath" a Java SDK Cumulative Fix. If the Java
SDK update was installed after an early Application Server Cumulative Fix,
then uninstall the Java SDK update first, and afterward uninstall the
Application Server Cumulative Fix. Then, reinstall the Java SDK Cumulative
Fix.
Alternatively, you can install a newer version of the Java SDK Cumulative
Fix (if available) to ensure the ORB is brought to the latest available
level.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|