|
Problem(Abstract) |
Temporary/test fixes applied to the
<wasroot>/classes directory can change product behavior following a
Fix Pack install |
|
|
|
Symptom |
Change In Behavior Following Fix Pack Install |
|
|
Cause |
Temporary/test fixes applied to the
<wasroot>/classes directory can change product behavior following a
Fix Pack install if allowed to remain in the <wasroot>classes
directory. |
|
|
Diagnosing the
problem |
On occasion, a temporary or test fix may be provided by
IBM® support. If install directions include copying the provided fix to
the <wasroot>classes folder then caution must be exercised while
applying a Fix Pack install.
The Update Installer tool does not consider the classes folder and will
not remove any fixes in that folder. You should receive a warning that
there are entries in the classes folder that should be removed. This
warning does not stop the update from being applied.
Code which remains in the <wasroot>/classes folder following Fix
Pack install takes precedence over other WebSphere® Application Server
binaries and may cause a regression for a particular component. |
|
|
Resolving the
problem |
For a change In behavior following Fix Pack Install
1) Verify that the updateinstaller completed successfully by checking the
update installer logs in the <wasroot>/logs/update folder
2) Verify that there are no files present in the <wasroot>classes
folder. If temporary or test fixes are in the <wasroot>classes
directory, remove the files from the <wasroot>classes directory and
restart WebSphere Application Server to see if this is the cause of the
problem.
3) If a change In behavior persists, check the IBM support site for known
issues or contact IBM WebSphere Application Server Support |
|
|