PI40212: REQUESTS ARE BEING ACCEPTED AND SERVED BEFORE ALL THE EAR IS STARTED.

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.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

• During the server startup, no request can come into the server
  until ALL the application are started.  However, if the
  application is restarted, then each WAR (within the EAR) can
  start serving a request as soon as that WAR is ready.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Full       *
  *                  Profile version 8.5.5 users of              *
  *                  WebContainer.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: A request could be accepted and         *
  *                      served by the server before its         *
  *                      target EAR application is started.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An EAR application can contain multiple web application
  archive (WAR) files. During the application start up, each WAR
  is available to accept and serve the requests for its
  resources as soon as the WAR is started.  However, if the WAR
  files have a dependency on each other, accepting and serving
  the requests for one WAR, while its dependent WAR is still
  starting up, might cause some issues (i.e resource not found,
  corrupt shared map).
  This problem does not happen during the server startup as no
  request is accepted until all deployed application are started.
  

Problem conclusion

• The WebContainer code was modified to not accept and serve any
  request until the whole EAR application is started.
  
  A new WebContainer custom property needs to be set to enable
  the behavior provided by this APAR:
  
  com.ibm.ws.webcontainer.deferServingRequestsUntilEarStarted =
  true (default is false)
  
  NOTE: setting this new property will delay the service for all
  requests until all the WARs inside the target EAR are started
  completely.  For example, if the EAR has 10 WARs and the first
  WAR is started completely, it can not accept and serve any
  request until all 10 WARs have started.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 8.5.5.8
  
  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP