IBM Support

PI74924: Job with java batch COMPLETED status moves to STOPPING status after shutdown in executor.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer running a batch job after experiencing a executor
    failure may notice some jobs status are no longer marked as
    COMPLETED.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Batch                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Job with Java batch COMPLETED status    *
    *                      moves to STOPPING status after shutdown *
    *                      in executor.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In certain cases in which a batch job execution is determined by
    the executor to be invalid, a cached record of the running
    execution is created, and when the executor server is ultimately
    stopped (or the batch component within the executor shutdown),
    the job instance/execution is set to STOPPING status, even if
    the instance had reached COMPLETED status.
    
    This can happen when the server aborted in the middle of
    execution and then the executor is restarting causing a
    redelivery of the previous batch JMS execution message, or if
    perhaps two restart messages were delivered to the same batch
    executor for the same job.
    
    Even if one valid restart execution message is consumed and
    processed and the job executes to completion, the cached aborted
    execution record is incorrectly "cleaned up" on shutdown, and
    the status is moved to STOPPING, incorrectly.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI74924

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-13

  • Closed date

    2017-02-15

  • Last modified date

    2017-02-15

  • 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 PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 June 2020