IBM Support

PI40870: NEW JOBS DO NOT START WHEN THE WEBSPHERE BATCH SCHEDULER IS TERMINATED ABNORMALLY WHILE AN EXISTING JOB IS RUNNING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In Websphere Application Server v8.5.5.4 and v8.5.5.5 a XXX
    job class is configured with max concurrent job setting of 1.
    In the IBM Batch JMC a job is submitted. While the submitted
    job is running, the scheduler is terminated abnormally. When
    the Job Console Server is restarted and another job that uses
    the XXX job class is submitted,the job does not run. The
    following message will be seen in the Job Logs:
    CWLRS0493I: Job XXX_ABCJOB:000156 cannot be dispatched at
    this time as its job class XXX is running with full capacity.
    

Local fix

  • Correct the database by executing the following:
    UPDATE LRSSCHEMA.JOBCLASSMAXCONCJOBS SET CONCJOBCOUNT = 0 WHERE
    JOBCLASSNAME = 'XXX';
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of WebSphere Extended Deployment      *
    *                  Compute Grid V8.0 and the batch function    *
    *                  of IBM WebSphere Application Server V8.5.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: New jobs do not start when the batch    *
    *                      scheduler is terminated abnormally      *
    *                      while an existing job is running        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In the WebSphere batch function a XXX job class is
    configured with max concurrent job setting. In the
    IBM Batch JMC a job is submitted.  While the submitted job
    is running, the scheduler is terminated abnormally.  When the
    Job Console Server is restarted and another job that uses
    the XXX job class is submitted, the job does not run.
    The following message will be seen in the Job Logs:
    CWLRS0493I: Job XXX_ABCJOB:000156 cannot be dispatched at
    this time as its job class XXX is running with full capacity.
    This issue is caused by the scheduler not decrementing the
    concurrent job count of jobs that were previously running
    before the scheduler was shut down unexpectedly and it is
    hitting the max concurrent jobs value so no more jobs are able
    to be submitted.
    

Problem conclusion

  • The solution for this fix was to check for jobs that did not
    complete properly before the scheduler shutdown and then
    decrement the concurrent job count to accurately represent the
    jobs that are currently running.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.6 and 8.5.5.8. Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • An interim fix is available upon request.
    

Comments

APAR Information

  • APAR number

    PI40870

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-11

  • Closed date

    2015-08-25

  • Last modified date

    2015-08-25

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022