Fixes are available
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
OSGi applications that contain blueprint.xml in bundle fragments do not start after updating Liberty. System was updated from: - Tivoli 8.1 + WAS Liberty 8.5.5.3 to - Tivoli 8.1.1 + WAS Liberty 8.5.5.5
Local fix
None available
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Liberty * * Profile users with OSGi applications that * * include OSGi bundle fragments that contain * * blueprint xml files. * **************************************************************** * PROBLEM DESCRIPTION: OSGi applications that contain * * blueprint xml in bundle fragments do * * not start after Liberty profile update * * to 8.5.5.4, 8.5.5.5 or 8.5.5.6. * **************************************************************** * RECOMMENDATION: * **************************************************************** A change was made in Liberty V8.5.5.4 to fix a transient failure in an internal automated test suite. This tightened up our logic around exactly when an OSGi application is deemed to have started, but accidentally broke OSGi application users in the rare case in which an OSGi bundle fragment contains blueprint xml.
Problem conclusion
Fixed by removing bundle fragments from the list of bundles whose blueprint containers we wait for in com.ibm.ws.app.manager.esa.internal.futures.ESAStartFuture.creat eFuturesForBundles(). The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.7. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
It may be possible for application developers to move blueprint xml files from bundle fragments to their host bundles.
Comments
APAR Information
APAR number
PI42400
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-04
Closed date
2015-06-19
Last modified date
2015-06-19
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
28 April 2022