Fixes are available
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
Rational Asset Manager bundle repositories accessed via HTTP do not always make the latest version of a bundle available to OSGi applications if the bundle has been previously imported by an OSGi application.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Rational Asset Manager * * bundle repositories accessed via HTTP * * do not always make the latest version * * of a bundle available to * * OSGi applications if the bundle has * * been previously imported by an * * OSGi application. * **************************************************************** * RECOMMENDATION: * **************************************************************** A Rational Asset Manager (RAM) OSGi bundle repository used by WebSphere Application Server (WAS) that is accessed via HTTP indicates whether one or more of the bundles it contains have been updated so that WAS may update cached data for these bundles. The mechanism by which changes were communicated was via a last-modified timestamp. However, this mechanism did not reliably indicate a change under all circumstances. This could result in an out-of-date cached version of a bundle being used by an Business Level Application (BLA) when that bundle had been previously imported by a BLA. The mechanism has been updated to remove this error, and is now implemented using HTTP ETags.
Problem conclusion
The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.8. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM93039
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-07-16
Closed date
2013-07-30
Last modified date
2013-07-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 November 2021