A fix is available
APAR status
Closed as program error.
Error description
When JavaServer Pages (JSP) are compiled at runtime, the classes created are placed in the servant specific temp directory (these are sub directories in the config HFS temp directory which contain the name of the servant plus the UUID). The servant specific temp directories are cleaned up when the server or servant is recycled, which means the JSPs will need to be recompiled again after a crash or normal recycle. These classes should be placed in the common server temp directory instead, which will persist through a recycle, and eliminate the need to recompile the JSPs.
Local fix
Precompiling the JSPs will place the classes in a different location, thus eliminating this problem all together.
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server version * * 7.0 users of multiple servant * * regions on z/OS * **************************************************************** * PROBLEM DESCRIPTION: Multiple instances of the same JSP * * class are created in different * * servant's specific temporary * * directory and get deleted when the * * server or servant is stopped. * **************************************************************** * RECOMMENDATION: * **************************************************************** When JSPs are compiled at runtime, the same generated classes are placed in each servant temporary directory. Those classes are then deleted when the server or servant is recycled. This is inefficient because it requires disk space to hold each copy of the same compiled classes. If the servant or server crash, these classes will not be cleaned up automatically. In addition, the deleted JSP classes have to be recompiled after each servant restarts.
Problem conclusion
The JSP container was modified to generate the compiled classes into a common server temporary directory which will also persist after the server or servant has restarted. APAR PK82687 is currently targeted for inclusion in Service Level (Fix Pack) 7.0.0.3 of WebSphere Application Server V7.0. 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
PK82687
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-16
Closed date
2009-03-19
Last modified date
2009-05-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
BBGUBINF BBOUBINF
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK45160
UP09/04/06 P F904
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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022