PI49508: At startup end users requests routed with HTTP 404 response

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

• AT STARTUP ENDUSERS REQUESTS ROUTED WITH  HTTP 404 RESPONSE
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The TCPChannel accepts connections when *
  *                      the server has not yet started.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The TCPChannel accepts connections during the server start up
  process before the applications or server has started. This
  behavior causes any request that comes into an application that
  is not ready to serve requests to get a HTTP 404 response with
  the message:
  "WebSphere Application Server Version V8.5 Liberty Profile -
  Context Root Not Found" .
  

Problem conclusion

• A new waitToAccept configuration option was added to the
  TCPChannel that will close the connections until the server is
  ready. This new option should be used with the acceptThread TCP
  option.
  
  To enable the new behavior add the following configuration
  options in the endpoint section of the server.xml
  
    <tcpOptions waitToAccept="true" acceptThread="true"/>
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.9.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP