Fixes are available
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
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris
APAR status
Closed as program error.
Error description
Problem desc: Customer gets 404 when he request servlet with /scope when server servlet by class name is enabled. Servlet class name is Scope.class (capital S). Customer gets 404 for all the following request with /Scope. WAS 6.1.0.5/RHEL
Local fix
a
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server version * * 6.1 users who access a web application by * * a servlet's classname. * **************************************************************** * PROBLEM DESCRIPTION: The webcontainer will fail any request * * to a servlet (by classname) that * * follows an incorrect request of the * * same servlet's name (but different * * case). * **************************************************************** * RECOMMENDATION: * **************************************************************** When serving servlets by classname, an initial request to an incorrect case-sensitive servlet name will also cause any subsequent correct case servlet requests to fail until the application is restarted. For example, if the classname is myServlet, the fist request to /servlet/myservlet will fail. A second request to the correct one (/servlet/myServlet) will also fail.
Problem conclusion
Applying this APAR and setting the web container custom property "com.ibm.ws.webcontainer.servletcasesensitive" will serve only the correct case-sensitive servlet. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.9. 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
PK42055
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-03-27
Closed date
2007-04-26
Last modified date
2007-04-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK42370
Modules/Macros
ENGINE
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
R61Z PSY
UP
Document Information
Modified date:
29 December 2021