PH15877: Angel stops without detecting active liberty servers.

APAR status

• Closed as program error.

Error description

• A liberty server that has registered with an Angel to
  perform authorized services may become unknown to that angel
  a short time after the server was started.
  
  This can cause a number of problems.   The angel is not
  aware that the Liberty server may want to drive angel
  specific services and will allow itself to terminate without
  concern for that server.   If the server attempts to drive
  an authorized service after its angel has terminated it will
  receive PC related ABENDs (ABEND code D6 is the most
  common).
  
  Other angel services that provide information on the server
  may also be affected while the Angel is still running.   Any
  modify commands that  provide information about active
  servers, such as f bbgzangl,DISPLAY,SERVERS,  will not
  display the liberty server.
  
  Also, any WOLA processes trying to connect to a liberty
  server may experience unpredictable problems.
  
  The above problems are caused by the liberty server dropping
  unique ENQs.  There is a circumvention to this.  Setting the
  following property in the bootstrap.properties file will
  avoid the ENQs from being dropped:
  
  equinox.start.level.thread.count=1
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty for z/OS                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Angel stops without detecting active    *
  *                      liberty servers.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A liberty server that has registered with an Angel to perform
  authorized services may become unknown to that angel a short
  time after the server was started.
  
  This can cause a number of problems.  The angel is not aware
  that the Liberty server may want to drive angel specific
  services and will allow itself to terminate without concern for
  that server.  If the server attempts to drive an authorized
  service after its angel has terminated it will receive PC
  related ABENDs (ABEND code D6 is the most common).
  
  Other angel services that provide information on the server may
  also be affected while the Angel is still running.  Any modify
  commands that  provide information about active servers, such as
  f bbgzangl,DISPLAY,SERVERS, will not display the liberty
  server.
  
  Also, any WOLA processes trying to connect to a liberty server
  may experience unpredictable problems.
  
  The above problems are caused by the liberty server dropping
  unique ENQs.
  

Problem conclusion

• Code has been modified to avoid releasing the ENQs too early.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 19.0.0.9.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Setting the following property in bootstrap.properties before
  starting your server will avoid this problem:
  
  equinox.start.level.thread.count=1
  

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

  LIBERTY PROF -

• Fixed component ID

  5655W6514

Applicable component levels