IBM Support

PI05557: THE TRANSACTIONAL WORK IN DESTROYJOBSTEP() NOT ROLLED BACK AFTER AN EXCEPTION HAS BEEN THROWN.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The transactional work in destroyJobStep() has not been rolled
    back after an error has occurred and the method has been left
    with a RuntimeException.
    
    System.out:  O£  10/01/13 10:02:22:670 CEST Oヘナ-  FATAL
    com.swissre.g32.manager.batch.step.G32AbstractBatchStep
    Exception during destroyJobStep java.lang.RuntimeException:
    Breaking Point thrown in order to test restart
    at
    com.swissre.g32.manager.batch.step.G32BreakingPointAdvice.throwA
    nError(G32BreakingPointAdvice.java:148)
    at sun.reflect.GeneratedMethodAccessor402.invoke(Unknown Source)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at
    org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdvi
    ceMethodWithGivenArgs(AbstractAspectJAdvice.java:627)
    at
    org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdvi
    ceMethod(AbstractAspectJAdvice.java:609)
    ....
    ....
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All WebSphere Extended Deployment Compute   *
    *                  Grid 8.x and WebSphere Application Server   *
    *                  8.5.5.x batch function users.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Transactional work in the               *
    *                      destroyJobStep() method does not get    *
    *                      rolled back after an exception is       *
    *                      thrown.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Transactional work in the destroyJobStep() method does not get
    rolled back after an uncaught exception is thrown. The batch
    container does not acknowledge the exception and the job may end
    normally
    

Problem conclusion

  • The batch container no longer ignores uncaught exceptions from
    the destroyJobStep() method of a batch step. Instead the
    exception is acknowledged by the batch container and the
    transactional work is rolled back.
    
    The fix for this APAR is currently targeted for inclusion in
    WebSphere Compute Grid 8.0.0.4 and also in WebSphere
    Application Server 8.5.5.2. Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?uid=swg27022998 or
    http://www.ibm.com/support/docview.wss?uid=swg27036319
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI05557

  • Reported component name

    WXD Z COMP GRID

  • Reported component ID

    5655V6201

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-06

  • Closed date

    2014-04-07

  • Last modified date

    2014-04-07

  • 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 Z COMP GRID

  • Fixed component ID

    5655V6201

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS8NUZ","label":"WebSphere Extended Deployment Compute Grid for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022