PK76810: MULTIPLE REQUESTS TO JSPS IN DIFF. APPLICATIONS BUT WITH SAME NAME, ROUTED TO DIFF. SERVANTS CAUSE CLASSNOTFOUNDEXCEPTION.

Fixes are available

APAR status

Closed as program error.

Error description

When multiple requests to the same JavaServer Pages (JSP) name
but belonging to different applications are routed to different
Servant Regions at the same time, a ClassNotFoundException
might occur.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.0.1 for z/OS                             *
****************************************************************
* PROBLEM DESCRIPTION: When JSPs are compiling at runtime on   *
*                      a z/OS server, a                        *
*                      ClassNotFoundException might occur.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem occurs only in a WebSphere z/OS server.  When JSPs
are compiled at runtime, the JSP Container manages the case
where multiple threads try to access same JSP file name to
compile it by allowing one thread to lock the JSP file name
before it is compiled.  If an instance arises where two or
more requests for the same JSP file name but belonging to
different applications need to be compiled at the same time,
there is a small window in which a ClassNotFoundException is
likely to occur.

Problem conclusion

The JSP Container code was modified to correct the problem.
The JSP file is now being locked prior to its translation and
unlocked after it finishes compiling.  When a thread fails to
lock the JSP, it will retry to obtain the file lock for that
JSP for up to 240 seconds.  If the lock is obtained, it will
check whether the JSP has been compiled.  If not compiled, it
will attempt to compile the JSP for up to 5 times before
giving up.  A user can increase the file lock or compilation
retrying time by setting the webcontainer's custom properties:

com.ibm.ws.jsp.zosFileLockRetrying = 240 (default)

com.ibm.ws.jsp.zosReCompile = 5 (default)

The custom properties are not case sensitive.

APAR PK76810 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 Change to the WebSphere Application
Server Version 6.0.x Information Center will be made
available in March, 2009.

The following descriptions of the new
com.ibm.ws.jsp.zosFileLockRetrying and
com.ibm.ws.jsp.zosReCompile  Web container custom
property will be added to the topic "Web container
custom properties:"

Changing the file lock time for a JSP

Use the com.ibm.ws.jsp.zosFileLockRetrying property to
specify, in seconds, the amount of time during which a
thread continues to try to obtain a lock on a JSP.

A JSP file is locked prior to the start of the compile
process, and unlocked after the compile process
completes. If a thread fails to lock a JSP, the thread
continues to try to obtain the file lock for that JSP
for up to 240 seconds. If the thread cannot obtains the
lock during this time interval, an error message is
issued. The thread does not make any additional attempts
to obtain a lock for the JSP.

Data type     Integer
Default       240

Avoid Trouble: This custom property is only available
in Version 6.0.2.35, and later.

Changing the number of times that a thread attempts to
compile a JSP

Use the com.ibm.ws.jsp.zosReCompile property to specify
how many times a thread should attempt to lock a JSP.

After a thread obtains the lock for a JSP, the thread
determines whether the JSP is already compiled. If the
JSP is not compiled, the thread tries to compile the JSP.

If after the specified number of tries, the thread cannot
compile the JSP, an error message is issued. The thread
does not make any additional attempts to compile the JSP.

Data type              Integer
Default                5

Avoid Trouble: This custom property is only available
in Version 6.0.2.35, and later.

Please refer to the following technote for instructions on
enabling WebContainer custom properties:
http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395

APAR PK76810 is currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.35 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
PK76810
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-12-03
Closed date
2009-02-04
Last modified date
2009-06-01

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

PK77353 PK86982

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R601 PSY UK46540
UP09/05/30 P F905

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:
28 December 2021

Tips

PK76810: MULTIPLE REQUESTS TO JSPS IN DIFF. APPLICATIONS BUT WITH SAME NAME, ROUTED TO DIFF. SERVANTS CAUSE CLASSNOTFOUNDEXCEPTION.

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 UK46540

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?