PM97023: CONSOLE OUTPUT FOR SERVER START COMMAND DOES NOT CURRENTLY INDICATE SERVER STARTUP FAILURES.

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
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

• Server startup failures that occur after the base framework has
  started are not properly indicated to the server via the
  "server start <servername>" command.  These failures could be
  due to an improper configuration parameter, port conflict,
  etc. and can occur when certain server configuration elements
  (such as config or httpEndpoint) have set the onError
  attribute to "FAIL".  In these cases, the command line tool's
  output indicates that the server started successfully when it
  did not - or possibly when it was intentionally shut down due to
  some error.
  
  The command line tool instead should indicate that an error
  occured during startup and that the log files will contain more
  information as to why it failed.
  

Local fix

• N.A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Core                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: The server start command indicates a    *
  *                      successful start despite server fail.   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The server start command line tool in the <WLP_HOME>/bin
  directory may indicate that the server has started
  successfully - it will even provide a Process ID (PID) for the
  started server - even though the server process may have
  stopped or failed. The reason for this is that the server
  start tool did not use the return code provided by the server
  process.
  Please note that due to the asynchronous nature of the Liberty
  Profile server startup process, the results from the server
  start tool may still be incorrect.  For example, it is
  possible that the server may start successfully but create
  threads of execution that are still starting other components
  such as stack products, third party applications, or other
  WebSphere components and one of these components may bring the
  server down after the server start tool output that the server
  started successfully.
  

Problem conclusion

• This fix provides the server start command line tool with a
  return code indicating success or failure of the server
  startup.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.2. 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