[TechNote] load-on-startup SERVLET IS INITIALIZED BEFORE FILTER

load-on-startup SERVLET IS INITIALIZED BEFORE FILTER

APAR status

• Closed as program error.

Error description

• load-on-startup servlets are initialized prior to filter
  initialize. This is contrary to servlet specification.
  

Local fix

• 
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: load-on-startup servlets are            *
  *                      initialized before filters are          *
  *                      initialized.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Java Servlet specification states that when a web
  application is started, the filter initialization step must be
  performed prior to initialization of load-on-startup servlets.
  The current server behavior initializes the filters at request
  time or after load-on-startup servlets are initialized when
  the following webcontainer custom property is set "
  com.ibm.ws.webcontainer.invokeFilterInitAtStartup = true
  (default = false)".
  

Problem conclusion

• The Webcontainer code is fixed to correct the order of the
  filter and the servlet initialization.
  To get this new behavior, these webcontainer custom properties
  need to be set :
  
  com.ibm.ws.webcontainer.initFilterBeforeInitServlet = true
  (default = false)
  com.ibm.ws.webcontainer.invokeFilterInitAtStartup = true
  (default = false) // This custom property was added by PK86553.
  
  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
  fix pack 7.0.0.25, 8.0.0.5, and 8.5.0.1.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980