IBM Support

PH10566: ISSUES WITH REMOTE PARTITION RESTART IF SERVER CRASHES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Ensure that remote partitions properly get marked failed and
    restartable should the server go down during their execution
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Batch                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Java Batch: Remote JVM partitions not   *
    *                      restartable after executor shutdown     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a Java Batch job or partition is running on an executor
    that shuts down suddenly, the status will continue to show as
    running, as there was no chance to mark the status as failed.
    
    For most jobs, this will be resolved the next time that executor
    is started after the shutdown. For a remote JVM partition,
    however, starting the executor again will not mark the partition
    failed, leaving the job in a non-restartable state.
    

Problem conclusion

  • This problem is resolved in Open Liberty by
    https://github.com/OpenLiberty/open-liberty/issues/8761.
    
    A new database table, REMOTEABLEPARTITION, has been added to the
    job repository. This table allows executors to keep track of
    their own remote partitions, allowing them to be marked failed
    when restarting after a shutdown.
    
    If your Liberty server is configured so that JPA can
    automatically create tables as needed, no special action is
    required. If you have table creation turned off in order to
    manage the job repository directly, you will not see the benefit
    of this fix until the new table is created. You can make use of
    the ddlGen utility to generate table creation statements you can
    use for this purpose.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 19.0.0.10.  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 number

    PH10566

  • Reported component name

    LIBERTY PROF -

  • Reported component ID

    5655W6514

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-03

  • Closed date

    2019-10-03

  • Last modified date

    2019-10-03

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"850","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2020