PI51375: Application Manager change to make time waiting for apps at star tup configurable

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

• Application Manager change to made time waiting for apps at
  startup configurable
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Liberty profile expects applications to *
  *                      start within a fixed 30 seconds         *
  *                      period.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Liberty profile has a fixed timeout of 30 seconds for
  applications to start. After the 30 second timeout expires two
  things happen: a message is output to the logs saying the
  application didn't start quickly enough; during server startup
  the server will stop waiting for the application to start and
  claim to be started, even though the application is not yet
  ready.
  

Problem conclusion

• The Application Manager code was modified to make the start
  timeout configurable. The new configuration option is called
  startTimeout with a default value of 30s. The value set in this
  configuration will act as a maximum, if all applications start
  before the timeout the server will start.
  
  To set this value to one minute add the following to
  server.xml:
  
  <applicationManager startTimeout="1m"/>
  
  
  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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP