IBM Support

JR57363: IF A NESTED BPEL MICROFLOW INVOKES THE BFM API, A NULLPOINTEREXCEPTION OCCURS WHEN THE MICROFLOW COMPLETES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a BPEL process invokes a microflow, and that microflow
    invokes the Business Flow Manager (BFM) API from within a
    snippet activity, you observe that the snippet runs
    successfully, but a NullPointerException occurs when the
    microflow completes:
    
    java.lang.NullPointerException
                    at
    com.ibm.bpe.engine.BpelProcessState.informWorkCompletionContract
    (BpelProcessState.java:1390)
                    at
    com.ibm.bpe.engine.BpelProcessState.endProcess(BpelProcessState.
    java:247)
                    at
    com.ibm.bpe.engine.BpelScopeState.finishScopeInstanceImpl(BpelSc
    opeState.java:2110)
                    at
    com.ibm.bpe.engine.BpelScopeStateRunning.finishScopeInstance(Bpe
    lScopeStateRunning.java:59)
                    at
    com.ibm.bpe.engine.BpelActivityKindComplexEnd.doActivate(BpelAct
    ivityKindComplexEnd.java:87)
    
    This issue occurs, for example, for the forceTerminate and the
    delete BFM API methods.
    
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    

Local fix

Problem summary

  • When a BPEL process invokes a microflow, parent context
    information for the microflow is initialized. It contains, for
    example, the parent?s template ID, which is required when the
    microflow completes. While BFM API methods like forceTerminate
    and delete are being invoked, this context changes to the
    context of the target process instance to run the API method.
    However, after this method returns, the microflow?s context is
    not restored correctly, which leads to the NullPointerException
    when the microflow completes because the parent information in
    its context is incorrect for this instance.
    

Problem conclusion

  • A fix is available for IBM BPM 7.5.1.2 on request from BPM
    L3 support, that ensures that the parent context is reset
    correctly.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57363

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-03

  • Closed date

    2017-02-23

  • Last modified date

    2017-02-23

  • 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 ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R751 PSY

       UP

  • R857 PSY

       UP

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

Document Information

Modified date:
23 February 2017