PK45107: EXCEPTION FROM SERVLET FILTER IS NOT PROPAGATED TO CLIENT

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

• If the filter that picked up the request throws an exception -
  that exception is not reported back down the stack to
  the user. Websphere  application server instead just reports a
  404 error instead, with no sign of the original exception from
  the filter.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server Version 6.1 *
  *                 users of filters.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Exceptions thrown within the filter     *
  *                      are not propagated to the client.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  While processing a request, the WebContainer does not send the
  proper status code to the client when an exception occurs in
  the filter code.
  For example, users often write filters to redirect a request to
  a different location to find a resource if it is not found
  using the original request's data. The WebContainer handles
  this by calling the application's filters before sending a 404
  status code.  If an exception occurs while processing the
  filter, the WebContainer should send a 500 status code instead
  of a 404.
  

Problem conclusion

• The WebContainer code was modified to check to see if there was
  an exception in the filter code before sending a 404 status
  code.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 6.1.0.13. 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:

Modules/Macros

• ENGINE
  

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

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