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
PK33090; 6.1: A filter that serves a file does not popup an alert message
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
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris
APAR status
Closed as program error.
Error description
A filter that serve every file *.js does not popup alert message in Websphere version 6.1 and where as the same code works fine in WebSphere version 6.0.2.x level.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server version 6.1 * * users. * **************************************************************** * PROBLEM DESCRIPTION: The Webcontainer throws a * * FileNotFoundException when a resource * * does not exist on the file system but * * a filter should find it. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a request is made for a file that does not exist at the location specified in the request the Webcontainer calls the filters (if any) associated with the request. If the filters were able to find the requested resource the request is supposed to continue on as normal. However the webcontainer is sending back a 404 error even though the filters were able to find the resource. Theorectically, this problem could arise with any application which has this type of a setup. However, most that seem to have this problem are Java Server Faces (JSF) applications. The way JSF constructs their pages often refers to a file, usually a JavaScript file, at a location where it does not physically exist. The file is usually packaged within a JAR file and has a different path to the file. Therefore when the Webcontainer attempts to find that file, it cannot and then processes the filters for that request. The filters then modify the request and point the Webcontainer to the proper path to the file. Even though the filters were processed properly, the Webcontainer still returns a 404 error.
Problem conclusion
The Webcontainer code was modified to continue processing the request if the filters were processed properly. In order for this to function properly the following Webcontainer custom property must be set to 'true': com.ibm.ws.webcontainer.invokefilterscompatibility 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
A test fix was provided to customers for 6.1.0.3.
Comments
APAR Information
APAR number
PK33090
Reported component name
WEBSPHERE BASE
Reported component ID
5630A3600
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-10-17
Closed date
2007-01-15
Last modified date
2007-02-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ENGINE
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R60A PSN
UP
R60H PSN
UP
R60I PSN
UP
R60P PSN
UP
R60S PSN
UP
R60W PSN
UP
R60Z PSN
UP
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