IBM Support

PH13367: WITH JAVA BATCH APPLICATIONS IN LIBERTY, JOB PARTITIONS FAIL DUE TO A DEADLOCK IN THE JOB REPOSITORY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running JSR 352 Java Batch applications in Liberty that
    have jobs with partitioned job steps, two of the job
    partitions
    fail due to a deadlock in the job repository.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty- Batch                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Job Partitions reported failing due to  *
    *                      a deadlock on Java Batch Job Repository *
    *                      tables                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Job partitions failed due to a deadlock in the job repository.
    The batch runtime datasource is on MSSQL.
    
    When using batch runtime's API getRunningExecutions, a deadlock
    was seen during the query (SELECT t0.JOBEXECID FROM
    dbo.WLPJOBEXECUTION t0, dbo.WLPJOBINSTANCE t1 WHERE
    (((t1.JOBNAME = @p0) AND (t0.BATCHSTATUS IN (@p1,@p2,@p3))) AND
    (t1.JOBINSTANCEID = t0.FK_JOBINSTANCEID)) ORDER BY t0.CREATETIME
    DESC)
    
    A deadlock was also seen performing a batch runtime operation
    updateJobExecutionAndInstanceOnStopBeforeServerAssigned which
    performs the update:
    (UPDATE dbo.WLPJOBEXECUTION SET BATCHSTATUS = @p0, ENDTIME =
    @p1, EXITSTATUS = @p2, UPDATETIME = @p3 WHERE (JOBEXECID =
    @P4)).  This is called when a stop of a job execution is
    performed, and the execution has not yet reached an endpoint.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH13367

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-13

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

  • Fixed component ID

    5724J0814

Applicable component levels

  • R855 PSY

       UP

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

Document Information

Modified date:
17 October 2021