Fixes are available
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
Very lengthy startup times can occur for web modules which are not metadata-complete and which have many JAR files. For example, a WEB module which has 100 or more JAR files with a total of 100MB or more of class data can see startup times of over one hour.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Extremely long start times for large * * web modules which contain CDI * * content. * **************************************************************** * RECOMMENDATION: * **************************************************************** The start times of large web modules which contain Contexts and Dependency Injection (CDI) content, or which are enabled for detection of CDI content, can be very long. Start times, which might have taken several minutes in a v8.5.5.0 application server, can grow to over an hour. The problem is specific to web modules which contain many classes in many JAR files. As relates to this APAR, web module start times are in proportion to both the number of classes in a web module and to the number of JAR files in a web module. The problem is specific to processing which is performed during application startup. The processing steps which have the problem are not performed during application deployment. The problem does not relate to metadata which is discovered during application deployment. New application deployments are not required after installing the APAR. The problem occurs because of scanning steps which were added to IBM WebSphere Application Server v9.0, and which were required to support CDI 1.2. Previous releases of the application server supported an earlier version of CDI which did not have the same scanning requirements. The main change introduced by CDI 1.2 is a requirement to scan web module JAR files which previously did not need to be scanned. As a possible work-around, a custom property is available which restricts scans to web module JAR files which contain a "beans.xml" CDI metadata file. In cases where CDI metadata is only present in JAR files which contain a "beans.xml", and where the number of JAR files which contain a "beans.xml" is small, the custom property should provide a large reduction to the application start time. However, when CDI content is present in JAR files which do not contain a "beans.xml", the custom property will not provide a solution. For more information in regards to the custom property, see http://www-01.ibm.com/support/docview.wss?uid=swg21983564.
Problem conclusion
A code update was made which improves the efficiency of steps which process CDI metadata. The result of the update should be to reduce application start times to several minutes, instead of an hour or more. The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.4. 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
PI77045
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-22
Closed date
2017-05-09
Last modified date
2017-05-09
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
04 May 2022