PK56247: PK31377 ONLY MADE CHANGES TO CALL FILTER IN RESPONSE TO 404 ERROR FOR JSP AND STATIC FILES, NOT SERVLETS.

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

APAR status

• Closed as program error.

Error description

• Customer is running 6.1.0.9 with come.ibm.ws.webcontainer.
  invokeFiltercompatibility set to true, and it's not working
  per PK31377. Lv. 3 team update indicates that PK31377 only
  made changes to call filters in response to a 404 error for
  jsp's and static files, but not servlets.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server users with  *
  *                 applications which use filters.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: If a servlet becomes unavailable the    *
  *                      filter(s) defined for the servlet       *
  *                      is (are) not called.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A filter defined for a servlet is called before the servlet is
  started and may, for example, forward or redirect the request
  to a different servlet. However, in a situation in which the
  servlet becomes unavailable for any reason, the filters are not
  called and a 404 - file not found error is returned.
  

Problem conclusion

• The webcontainer has been updated to also call filters defined
  for a servlet when the servlet is unavailable.
  
  However, in order to enable the behavior provided by this APAR
  the following existing webcontainer custom property must first
  be set to true:
  
  com.ibm.ws.webcontainer.invokeFiltersCompatibility.
  
  This custom property is not case sensitive. Please refer to
  the following technote for instructions on enabling
  webcontainer custom properties:
  
  http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395
  
  The fix for this APAR is currently targeted for inclusion in
  fixpacks 6.0.2.27 and 6.1.0.15. 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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP