PM95822: Container restart fails with IBM JDK 7

APAR status

• Closed as program error.

Error description

• When the restart logic after disconnect from the catalog
  server occurs, the child process started to replace the
  current container process fails to start correctly.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of eXtreme Scale that use IBM SDK     *
  *                  Java                                        *
  *                  Technology Edition Version 7.               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Container servers do not restart        *
  *                      correctly after being disconnected from *
  *                      the catalog server.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  With IBM SDK Java Technology Edition Version 7,  a problem with
  parsing the Java command line of the restarted container process
  exists.  As a result, the command line does not wait for the
  previous container process to finish stopping.  The
  disconnected server was also not being stopped with the
  Server.DISCONNECTED_SERVER_STOP return code, causing the
  disconnected server to take longer to stop. Both of these
  problems were fixed with this APAR.
  

Problem conclusion

• An interim fix is available for this APAR.
  

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

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R711 PSY

     UP

• R850 PSY

     UP

• R860 PSY

     UP