Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Runtime processing of web modules (WAR files) builds a list of files in the WAR to be used as a cache. More files are included in the list in v7.0 than in v6.1 or prior releases. The additional listing is caused by new processing requirements, in particular, requirements introduced by Java EE 5 annotations processing. The additional listing can cause applications migrated from v6.1 or earlier to v7.0 to start much more slowly, as additional time and memory is used in creating the list of Java "File" objects for each file in the WAR. An option is required for v7.0 to allow particular files to be omitted from the list to provide performance similar to that which was provided by v6.1.
Local fix
none at this time.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 and V8.0. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server takes * * a long time to start because of the * * amount of time taken to process * * application files. * **************************************************************** * RECOMMENDATION: * **************************************************************** The application server builds a list of all files in web modules during application start to be used as a cache. A Java "File" object is created for each file in the list. The cache improves performance during annotation scanning. However, for web modules containing many files (10,000 or more), building this cache can consume a lot of memory and increases application start time. Therefore, it is beneficial to reduce the size of the cache by not including some files.
Problem conclusion
This APAR provides the following JVM custom property to allow you to specify directories that are not to be included in the file list cache: "org.eclipse.jst.j2ee.commonarchivecore.FILTERBINARIES" This property should be set to the names of directories (relative to the root of web modules (WAR files)) which are to be ignored when building the file list cache during application start. Files beneath these directories, their subdirectories, and so on will not be included in the file list cache. The property applies only to web modules. The directory names listed in the property are filtered from ALL web modules in ALL applications. The property has no effect during deployment. Also, the property has no effect at application start if the application contains the setting useMetadataFromBinaries=true in the deployment.xml. See: http://tinyurl.com/kunlh9a The value of the JVM custom property is a list of paths, relative to the enclosing web module, with semicolon characters (";") used as the delimiter between path values. Forward slash characters ("/") must be used within the path values. For example, an application contains web modules named big.war and bigger.war. Each contains a large number of files. The majority of the files are beneath four directories: bigger.war/staticData/html bigger.war/staticData/css bigger.war/dojo big.war/dojo To filter these locations, set the JVM custom property to: org.eclipse.jst.j2ee.commonarchivecore.FILTERBINARIES= staticData/html;staticData/css;dojo Alternatively, you could set the property to ignore the entire "staticData" directory tree: org.eclipse.jst.j2ee.commonarchivecore.FILTERBINARIES= staticData;dojo The JVM custom property MUST NOT be set to a location which contains active application files relevant to Java EE; for example, class files, JAR files, deployment descriptors, other XML files and so on. That means that these four locations MUST NOT be filtered: META-INF WEB-INF WEB-INF/classes WEB-INF/lib Subdirectories beneath any of these locations MAY be filtered provided they contain no active files relevant to Java EE. This functionality is used to reduce application start times. The functionalilty has no effect on application deployment times. To improve deployment times for WARs with a large number of files, consider moving some of the files out of the WAR, and then configure extended document root; see: http://tinyurl.com/ku2fkay The key measure of the application which is relevant to this APAR is the NUMBER of files beneath the web modules. The size of the individual files is not relevant. This property is not intended for improving annotation scanning performance. For annotation scanning performance, use annotation filtering; see: http://tinyurl.com/m797drd Simple file names (instead of directory names) may also be listed in the custom property value, but that provides little benefit. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.19 and 8.0.0.1. 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
PM37942
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-04-28
Closed date
2011-08-09
Last modified date
2014-04-22
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
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021