IBM Support

JR56045: YOU RECEIVE A NULLPOINTEREXCEPTION WHEN USING AD HOC ACTIVITIES WITH PRECONDITIONS IN A LINKED PROCESS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you run a process with a linked process activity that has
    an implementation that contains ad hoc activities, you get a
    NullPointerException in at least one of the following scenarios:
    
    - You run the process on IBM Process Center and the hierarchy of
    linked processes spans across processes defined in toolkits for
    which you last modified the top-level process and the deepest
    nested process but kept a process in between unchanged.
    
    - You use a dynamic process defined as the implementation of a
    linked-process activity.
    
    You see the following warning in the SystemOut.log of the
    server:
    
    [6/6/16 13:15:53:071 CEST] 0000014e PreconditionD W
    com.lombardisoftware.bpd.runtime.engine.cases.PreconditionDefini
    tionsCache getBPDPreconditions Unable to find BPDPreconditions
    for a waiting activity
    
    You also see the following stack trace:
    
    java.lang.NullPointerException
    at
    com.lombardisoftware.bpd.runtime.engine.BPDAdhocActivityService.
    prepareWaitingActivityInstance(BPDAdhocActivityService.java:583)
    at
    com.lombardisoftware.bpd.runtime.engine.BPDAdhocActivityService.
    addReferenceForWaitingActivitiesToExecutionContext(BPDAdhocActiv
    ityService.java:736)
    at
    com.lombardisoftware.bpd.runtime.engine.BPDAdhocActivityService.
    initiateListOfAdhocActivities(BPDAdhocActivityService.java:150)
    at
    com.lombardisoftware.bpd.runtime.engine.BPDAdhocActivityService.
    initiateAdhocActivities(BPDAdhocActivityService.java:134)
    at
    com.lombardisoftware.bpd.runtime.engine.workresult.StartEventCom
    pletedWorkResult.execute(StartEventCompletedWorkResult.java:67)
    at
    com.lombardisoftware.bpd.runtime.engine.BPDEngine.executeTreeNod
    e(BPDEngine.java:421)
    ... 145 more
    

Local fix

Problem summary

  • When the definition of the preconditions of an ad hoc activity
    is to be looked up, the diagram of a nested linked process is
    not properly looked up, potentially because it's using the
    process definition from an incorrect toolkit version. For a
    linked-process activity with a dynamic linked process, the
    diagram of that dynamic linked process is not considered.
    

Problem conclusion

  • A fix will be included in an upcoming IBM Business Process
    Manager (BPM) V8.5 cumulative maintenance vehicle.
    
    To determine whether the cumulative fix is available and
    download it if it is, complete the following steps on Fix
    Central:
    
    1. On the Select product tab, select WebSphere as the product
    group, IBM Business Process Manager with your edition from the
    WebSphere options, All as the installed version, and All as the
    platform, and then click Continue.
    2. Select Text, enter ?cumulative fix?, and click Continue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR56045

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    857

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-07

  • Closed date

    2016-08-19

  • Last modified date

    2016-08-19

  • 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

  • R857 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":"857","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 August 2016