Fixes are available
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
For Liberty Profile 8.5.5.6 with cdi 1.2 the startup time is much slower than Liberty Profile 8.5.5.3 with cdi 1 Performance improvement for JavaEE6 applications working with cdi 1.0 migrating to cdi 1.2
Local fix
disable CDI and lose CDI functionality
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile - Contexts and * * Dependency Injection (CDI) * **************************************************************** * PROBLEM DESCRIPTION: An application with a large number of * * jar files that used to work on cdi 1.0 * * might experience slow startup if cdi- * * 1.2 feature is enabled. * **************************************************************** * RECOMMENDATION: * **************************************************************** In CDI 1.0, if an archive does not have a beans.xml then CDI ignores it completely. In CDI 1.2, it is no longer true and that can have a negative impact on startup performance, particularly for large applications which do not use CDI.
Problem conclusion
To match the CDI 1.0 performance and behaviour, the archives that do not have a beans.xml file will be ignored if the setting <cdi12 enableImplicitBeanArchives="false"/> is specified in the server.xml. This is only intended to be used when deploying old CDI 1.0 applications on cdi 1.2 feature and do not wish to use implicit bean archives. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.8. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
no
Comments
APAR Information
APAR number
PI47250
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-08-20
Closed date
2015-10-08
Last modified date
2015-10-08
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