PM90737: NULLPOINTEREXCEPTION IN JOB EXECUTION SETUP ON ENDPOINT CAUSES JOBS TO BE STUCK IN SUBMITTED STATE.

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

• The following NullPointerException occurs during job execution
  setup:
  
  java.lang.NullPointerException
  at
  com.ibm.ws.batch.BatchJobControllerWork._cleanUpAndShutdownOnErr
  or(Batch
  JobControllerWork.java:426)
  at
  com.ibm.ws.batch.BatchJobControllerWork.run(BatchJobControllerWo
  rk.java:
  232)
  at
  com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java
  :269)
  at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:229)
  at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:795)
  at
  com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithE
  xecution
  ContextImpl.java:222)
  at
  com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:20
  6)
  at java.lang.Thread.run(Thread.java:770)
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere Extended Deployment      *
  *                  Compute Grid 8.0 and the batch function of  *
  *                  WebSphere Application Server.               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Problem initializing job log            *
  *                      processing during early stages of job   *
  *                      execution on endpoint can leave jobs    *
  *                      "stuck" in 'submitted' state.           *
  *                      One such problem occurs when an         *
  *                      extraneous file in a managed job log    *
  *                      directory causes job log                *
  *                      initialization to fail.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A problem initializing job log handling for a given job was
  handled incorrectly by the runtime on the endpoint server.
  This led to a further problem where the job status wasn't
  getting communicated and managed correctly.  So rather than
  the job appearing to have failed and been put into
  "restartable" state, the job appears to be stuck in
  "submitted" state (still in "submitted" state since job log
  initialization happens early on in the job lifecycle).
  One particular problem initializing job log handling provoking
  the original symptom occurs when extraneous files are added to
  "managed" job log subdirectories.
  For example, if directory:
  ...PROFILE_HOME.../joblogs/<endpointServer>
  which usually contains subdirectories:
  section1, section2, ..., sectionN,
  also contains an extra file, (perhaps section1.zip if this
  subdirectory was zipped up in-place), then this symptom could
  be seen.
  

Problem conclusion

• The endpoint will close this gap by updating the job status to
  'restartable' when an exception is thrown.
  
  In addition an update was made to try to avoid the particular
  problem with the extraneous file in the job log directory, but
  it is still recommended to avoid writing or adding to these
  directories manually.
  
  APAR PM90737 is currently targeted for inclusion in Service
  Level (Fix Pack) 8.0.0.4 of WebSphere Compute Grid 8.0.
  
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?uid=swg27022998
  

Temporary fix

• An interim fix is available upon request.
  

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