PM90388: SCHEDULEREXCEPTION: UNABLE TO GET JOB NUMBER

8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.4: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 4
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.0.0.5: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 5
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Job Scheduler throws the following exception:
  
  [3/8/13 16:40:55:680 CST] 00000059 JobSchedulerM E   Caught
  exception inJobSchedulerMDB.submitJob:
  java.lang.RuntimeException: Login failure  during job
  submission: java.lang.RuntimeException:
  JobSchedulerMDB.SecureSubmitter: caught exception
  com.ibm.websphere.longrun.SchedulerException: Unable to get job
  number
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Compute Grid 8.0 and *
  *                  beyond                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: In certain scenarios, unique job id     *
  *                      numbers were unobtainable. This led to  *
  *                      batch jobs not being submitted.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Due to the manner by which unique job identifier numbers were
  being obtained by the compute grid framework, in certain
  scenarios, a job identifier number would be unobtainable. This
  led to the job in question not being submitted for processing.
  

Problem conclusion

• A new manner for obtaining job identifier numbers using a
  database sequence operator was devised and implemented. Using a
  sequence operation for id number generation allowed for atomic
  creation in a highly performant manner. With this fix in place
  job identifier numbers are obtained without interruption thus
  allowing the jobs themselves to be successfully submitted.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 8.0.0.4. Please refer to the Recommended Updates page
  for delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27022998
  

Temporary fix

Comments

APAR Information

• 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

  WXD COMPUTE GRI

• Fixed component ID

  5725C9301

Applicable component levels

• R800 PSY

     UP