IBM Support

JR47013: SPECIFIC ERRORS ARE NOT CAUGHT BY ERROR INTERMEDIATE EVENT IF NESTED SERVICE IS IN A TOOLKIT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In some scenarios, Error Intermediate Events configured to catch
    specific errors within services do not work as expected.
    
    Under the following conditions, the Error Intermediate Event
    fails to
    catch the specified error at runtime:
    - The Error Intermediate Event is placed on a Nested Service
    activity
    and is configured to catch a specific error (instead of catching
    all
     errors)
    - The Nested Service resides in a Toolkit referenced by the
    business
     application
    - The error thrown by the nested service has an Error data
    payload
    

Local fix

  • n/a
    

Problem summary

  • Problem fixed
    

Problem conclusion

  • iFix available on top V8011
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR47013

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-20

  • Closed date

    2013-08-12

  • Last modified date

    2013-08-12

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R801 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
12 August 2013