PM87666: DESTROYJOBSTEP METHOD NOT INVOKED AFTER EXCEPTION FROM LAST CHECKPOINT.

8.0.0.3: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 3
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
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

APAR status

• Closed as program error.

Error description

• destroyJobStep() not invoked after exception from last
  checkpoint
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere Extended Deployment      *
  *                  Compute Grid 8.0 and the batch function of  *
  *                  WebSphere Application Server.               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Exception not visible in                *
  *                      JobStepContext in destroyJobStep()      *
  *                      method. Also java.util.logging          *
  *                      entries are not getting redirected to   *
  *                      job logs.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The first problem fixed involves the step manager's exception
  handling, which was losing the original exception and causing
  the getUserException() method on the
  com.ibm.batch.api.context.JobStepContext API class to return a
  secondary exception rather than the one representing the first
  failure.  This was noticable during the destroyJobStep()
  method, and prevented this method from accurately accessing
  the original failure.
  A second problem fixed also involved the step manager and its
  creation of a java.util.logging Handler to direct any
  application log messages issued via a java.util.logging Logger
  to the Compute Grid / batch job logs.   The job log function
  was designed to be configurable to intercept java.util.logging
  log messages for a given logger withing a given step.
  

Problem conclusion

• The exception handling has been fixed.
  
  Note that sending java.util.logging log messages to the job
  log can be accomplished with an xJCL step definition such as
  the following:
  
  
     <job-step name="MyJDBCStep1">
        ...
      <batch-data-streams>
           ...
      </batch-data-streams>
      <props>
        <prop name="BATCHRECORDPROCESSOR"
  value="com.ibm.websphere.batch.samples.tests.steps.Infrastructur
  eVerificationTest"/>
        <prop name="debug" value="true"/>
       <prop name="com.ibm.websphere.batch.JavaUtilLoggerName"
  value="my.logger.name"/>  <!-- E.g. the class or package name
  -->
      </props>
    </job-step>
  
  The fix for this APAR is currently targeted for inclusion in
  Service Level (Fix Pack) 8.0.0.3 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

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM87839

Fix information

• Fixed component name

  WXD COMPUTE GRI

• Fixed component ID

  5725C9301

Applicable component levels

• R800 PSY

     UP