IBM Support

JR56529: YOU SEE AN ACTIVE PROCESS INSTANCE WITHOUT ACTIVE TASKS, ACTIVITIES, OR EVENTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you run a process instance that has a conditional activity
    and that conditional activity has at least one boundary event,
    the instance stays in the active state although all tasks and
    required ad hoc activities are completed and no intermediate
    events are waiting.
    

Local fix

  • When you require an activity to run based on a condition and you
    also need boundary events on that activity, do not define the
    activity to be conditional. Instead, use an exclusive gateway
    before the activity to either run the activity or prevent the
    activity from running.
    

Problem summary

  • When you define an activity to be conditional, its condition is
    evaluated when a token reaches it to check if the activity
    should run or to be skipped. This condition was incorrectly
    evaluated again when the activity was completed. If the
    condition was false during the second evaluation, processing the
    activity stopped and the process continued. At that time,
    tokens for boundary events on this activity were not removed
    and, therefore, caused the instance to stay in the active state.
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Problem conclusion

  • A fix will be included in IBM BPM V8.5.7 cumulative fix 2016.09
    that ensures the tokens of boundary events are correctly cleaned
    up and that allows you to change the behavior so the business
    process definition (BPD) engine BPM evaluates the condition only
    when the activity is created and not when it is completed.
    
    To determine whether the cumulative fix is available and
    download it if it is, complete the following steps on Fix
    Central:
    
    1. Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
    2. Select Text, enter ?cumulative fix?, and click Continue.
    
    To change the behavior of the BPD to check the activity
    condition only when the activity is created, edit your IBM
    Process Center and IBM Process Server 100Custom.xml files to
    match the following entry:
    
    <server>
      <bpd-engine merge="mergeChildren">
         <evaluate-condition-only-on-activity-creation
          merge="replace">
           true
         </evaluate-condition-only-on-activity-creation>
      </bpd-engine>
    </server>
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR56529

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-19

  • Closed date

    2016-09-21

  • Last modified date

    2016-09-21

  • 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

  • R856 PSY

       UP

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

Document Information

Modified date:
21 September 2016