PI27372: CALL TO GETREQUESTDISPATCHER INSIDE FILTER INIT METHOD CAUSES AN EXCEPTION

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Calling a getRequestDispatcher inside the filter init met
  hod makes the whole filter list to fail. Only the previous
  filters initialized before the exception occurred work.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:   All users of IBM WebSphere Application     *
  *                  Server Liberty Profile version 8.5.5        *
  ****************************************************************
  * PROBLEM DESCRIPTION: A                                       *
  *                      java.util.ConcurrentModificationExcepti *
  *                      on occurs during the initialization of  *
  *                      application defined filters             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If additional filter mappings are added to the existing filter
  mappings list, a ConcurrentModificationException is thrown.
  After the exception is thrown, the remaining filters in the list
  are not added. A known cause for this is calling the
  getRequestDispatcher method during the filter initialization.
  An example of this exception would be:
  [1/29/14 11:29:12:633 CST] 00000025
  com.ibm.ws.webcontainer.webapp                               E
  SRVE0267E: Error occured while initializing filters: {0}
  java.util.ConcurrentModificationException
      at
  java.util.ArrayList$Itr.checkForComodification(ArrayList.java:81
  9)
      at java.util.ArrayList$Itr.next(ArrayList.java:791)
      at
  com.ibm.ws.webcontainer.filter.WebAppFilterManager.init(WebAppFi
  lterManager.java:217)
      at
  com.ibm.ws.webcontainer.osgi.webapp.WebApp.initializeFilterManag
  er(WebApp.java:854)
      at
  com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinall
  y(WebApp.java:1076)
      at
  com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:965
  )
      at
  com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:603
  8)
  

Problem conclusion

• The Web Container code was changed so that the filter mappings
  were copied to a new list so that the
  ConcurrentModificationException does not occur.
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.4.  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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP