PK69220: SLOW APPLICATION STARTUP

Fixes are available

APAR status

Closed as program error.

Error description

For very large applications with a large number of files and
directories, application startup time has increased by a
significant amount when moving from v5.0 to v5.1/v6.x.  This is
due to new code in later versions of WebSphere that search the
application installation directories for TLD (taglib descriptor)
files.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.0.1. for z/OS and distributed platforms. *
****************************************************************
* PROBLEM DESCRIPTION: During the startup of an application    *
*                      a lot of time is spent searching for    *
*                      TLD files within the application.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The JavaServer Pages (JSP) Container recursively searches for
TLD files within an application's WEB-INF directory and also
inside of JAR files that are in the WEB-INF/lib directory
while starting the application.  If the application is large
and contains numerous directories, this can increase the time
it takes to start the application.  If an application does not
use TLD files or all of the needed TLD files are specified in
the application's web.xml file, this search is unnecessary.

Problem conclusion

The JSP Container was modified to add a JSP attribute which
will allow a user to disable the implicit searching for TLD
files within an application.  The JSP attribute is called
'disableTldSearch' and the value must be set to 'true'.  This
attribute is set in the application's ibm-web-ext.xmi file.
An example entry is:
<jspAttributes xmi:id="JSPAttribute_1" name="disableTldSearch"
value="true"/>

With this attribute set in the application's ibm-web-ext.xmi
file, any TLD files to be used in the application must be
specified in the web.xml file as per the JSP Specification.

Alternatively, a Web Container custom property called
'com.ibm.wsspi.jsp.disableTldSearch' can be set to 'true' if
this behavior is desired for all applications within the Web
Container.

APAR PK69220 requires changes to documentation.

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:

http://www.ibm.com/software/webservers/appserv/library

The following Changes to the z/OS version of the
WebSphere Application Server Version 6.0.x
Information Centers will be made available.

The following description of the
com.ibm.wsspi.jsp.disableTldSearch Web conatiner
custom property will be added to the topic "Web
container custom properties:"

Improving the startup time for large applications

The com.ibm.wsspi.jsp.disableTldSearch custom
property can be used to improve application startup
time. By default, when an application starts, the
JSP engine searches the application installation
directories for the taglib descriptor (TLD) files.
This search process might increase the startup time
for large applications with a large number of files
and directories. To disable this search process,
use the following name-value pair:

Name                                   Value
com.ibm.wsspi.jsp.disableTldSearch     true

The following description of the disableTldSearch
will  be added to the topic "JSP engine configuration
parameter:"

disableTldSearch

If this option is set to true, when an application
starts, the JSP engine does not search the application
installation directories for the taglib descriptor
(TLD) files. If this option is set to false, when an
application starts, the JSP engine searches the
application  installation directories for the TLD
files. The default for this parameter is false.

There is a Web container custom property,
com.ibm.wsspi.jsp.disableTldSearch, that can be used to
specify whether, when an application starts, the JSP engines
in all Web modules installed in a server do not search the
application installation directories for the TLD files. If
conflicting values are set for the Web container
custom property and the JSP engine option, the setting for
the JSP engine option takes precedence.

APAR PK69220 currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.33 of WebSphere Application Server V6.0.1
for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK69220
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
601
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-07-17
Closed date
2008-10-23
Last modified date
2009-03-16

APAR is sysrouted FROM one or more of the following:

PK69219
APAR is sysrouted TO one or more of the following:

PK82621

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R601 PSY UK43592
UP09/02/11 P F902

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK69220: SLOW APPLICATION STARTUP

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R601 PSY UK43592

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?