Fixes are available
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Solaris
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for HP-UX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Linux
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Windows
6.1.0.7 WebSphere Application Server V6.1 Fix Pack 7 for AIX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for i5/OS
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
PK37124; 6.1.0.3: Application errors (404, 500) when accessing precompiled JSPs
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris
APAR status
Closed as program error.
Error description
Users Affected: Customers with WebSphere Application Server at service pack levels 6.1.0.3 and 6.1.0.5, on distributed systems, who have precompiled JSPs that use JDK1.5 language features will encounter this problem. For example, "enum" is a JDK1.5 language feature that will encounter this problem. . This problem does not occur on Z/OS installations. Problem Symptoms: For this problem, JSP precompilation completes successfully, however the JSP pages cannot be loaded because their associated JSP classes cannot be found when attempting to load the JSP page. This problem results in an HTTP error code 404 when attempting to access the JSP page. For example: Error 404: SRVE0203E: Servlet [/jdkLevel15.jsp]: org.apache.jsp._jdkLevel15 was found, but is missing another required class. This problem also results in exceptions in the server logs: [11/18/06 13:00:33:473 EST] 0000001d ServletWrappe E [Servlet Error]-[_dontKeepGeneratedClassfiles.class]: java.lang.ClassNotFoundException: _dontKeepGeneratedClassfiles.class at com.ibm.ws.classloader.CompoundClassLoader.findClass (CompoundClassLoader.java:472) at com.ibm.ws.classloader.CompoundClassLoader.loadClass (CompoundClassLoader.java:373) at java.lang.ClassLoader.loadClass(ClassLoader.java:563) at com.ibm.ws.jsp.webcontainerext.JSPExtensionClassLoader. _loadClass(JSPExtensionClassLoader.java:128) at com.ibm.ws.jsp.webcontainerext.JSPExtensionClassLoader. loadClass(JSPExtensionClassLoader.java:67) ... additional lines omitted ... Problem Resolution: This problem may be avoided by precompiling only those JSPs that have JDK1.4 and earlier language features, or by not precompiling JSP that have JDK1.5 language features. The recommended solution for this problem is to install the ifix "6.1.0.3-WS-WAS-IFPKPK37124.pak". The ifix is applicable to WebSphere Application Server service levels 6.1.0.3 and 6.1.0.5. The fix is integrated in the WebSphere Application Server at service level 6.1.0.7. The fix replaces the prerequisite JAR file "org.eclipse.jdt.core_3.2.1.v_677_R32x.jar" with the earlier version, "org.eclipse.jdt.core_3.2.0.v_671.jar", which does not have the problem. The fix also removes the earlier version of the prerequisite JAR, "org.eclipse.jdt.core_3.1.2.jar", which is no longer in use. Important Note: This APAR PK37124 and associated ifix "6.1.0.3-WS-WAS-IFPK37124.pak" supercede the prior APAR PK34926 and its associated ifix "6.1.0.3-WS-WAS-IFPKPK34926.pak". The ifix for APAR PK34926 corrects the JSP precompilation problem, but introduces a new problem where the server will fail to start in "RESTRICTED" mode. Installation of PK37124 is necessary to allow server startup in "RESTRICTED" model. Restricted mode is enable by setting the server attribute "access to internal server classes" to "restrict". With the ifix for PK34926 installed, an attempt to start a Deployment Manager or an Application Server in restricted mode will fail with the following error: ADMU3011E: Server launched but failed initialization. In addition, the startServer log will contain the following error: ADMU3002E: Exception attempting to process server [serverName] ADMU3007E: Exception com.ibm.websphere.management.exception.NoServerDefinedException: No configuration defined for server: [serverName]
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users at * * service pack levels 6.1.0.3 and 6.1.0.5, * * on distributed systems who have precompiled * * JSPs that use JDK1.5 language features will * * encounter this problem. For example, "enum" * * is a JDK1.5 language feature that will * * encounter this problem. * * * * This problem does not occur on Z/OS * * installations. * **************************************************************** * PROBLEM DESCRIPTION: JSPs fail to load or the server fails * * to start in restricted mode * **************************************************************** * RECOMMENDATION: * **************************************************************** There are two possible problems that can be encountered: 1) JSP precompilation completes successfully, however the JSP pages cannot be loaded because their associated JSP classes cannot be found when attempting to load the JSP page. This problem results in an HTTP error code 404 when attempting to access the JSP page. For example: Error 404: SRVE0203E: Servlet /jdkLevel15.jsp : org.apache.jsp. _jdkLevel15 was found, but is missing another required class.
Problem conclusion
The fix replaces the prerequisite JAR file "org.eclipse.jdt.core_3.2.1.v_677_R32x.jar" with the earlier version, "org.eclipse.jdt.core_3.2.0.v_671.jar", which does not have the problem. The fix also removes the earlier version of the prerequisite JAR, "org.eclipse.jdt.core_3.1.2.jar", which is no longer in use. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.7. 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
PK37124
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2007-01-09
Closed date
2007-01-12
Last modified date
2015-06-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
WCCM
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
Document Information
Modified date:
28 December 2021