IBM Support

PI93514: JOB PURGE REQUEST DELETES THE BATCH DB RECORDS EVEN WHEN THE EXECUTOR JVM IS STOPPED.

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

  • When we send a job purge request to a Liberty server, the
    purge
    request would be redirect to the executor server where the
    job
    was processed.
    If the executor server is running at that time, both the job
    log and the related db records are deleted. This is normal.
    But if the executor server is stopped, the purge request is
    failed to be redirected, thus the job log is not deleted.
    But
    the related db records are deleted by the JVM that received
    the
    purge request. Thus, even if we rerun the purge request, it
    doesn't try to delete the job log. So we need to delete the
    unnecessary job log manually.
    

Local fix

  • delete the job log manually
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Batch                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Java Batch job purge deletes database   *
    *                      records even after encountering failure *
    *                      during a multi-instance purge           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Java Batch purge operation has two separate steps: delete
    the job log files from the filesystem, and then delete the
    database records associated with the job instance. When
    executing a purge that includes multiple instances in one
    command, the server may encounter an error during the file
    deletion (e.g. the server hosting the logs is unavailable at the
    time) but continue to delete the job records from the database.
    This is not intended behavior, as the database records should
    only be deleted upon successful completion of the file purge
    unless the purgeJobStoreOnly parameter is set.
    

Problem conclusion

  • Checks have been modified within the server to ensure that
    deletion of the database records is always contingent on
    successful completion of the filesystem delete actions. This
    will prevent database entries from being deleted when any kind
    of error occurs during the file purge step.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 18.0.0.2.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • If database records for a job are deleted while job log files
    still remain, the Batch purge operation will no longer be able
    to delete them, but the job log files may be safely ignored or
    deleted by the user (manually, e.g. using HFS commands like
    'rm').
    

Comments

APAR Information

  • APAR number

    PI93514

  • 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

    2018-02-07

  • Closed date

    2018-04-10

  • Last modified date

    2018-04-10

  • 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



Document information

More support for: WebSphere Application Server

Software version: CD0

Reference #: PI93514

Modified date: 10 April 2018


Translate this page: