IBM Support

JR57437: THE INSTANCE FAILS WHEN YOU RUN THE SAME TASK TWICE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When user tasks of a process are implemented by a heritage human
    service that has multiple coach steps, a user might start the
    human service for the same task more than once in multiple
    browser windows or browser tabs.
    Using IBM Process Portal, for example, a user might open the
    task in a new window if the corresponding option is set.
    For another example, the user might click the link of an email
    notification from IBM Business Process Manager (BPM) more than
    once.
    In either of these examples, the human service is navigated
    concurrently in the different browser windows or tabs, leading
    to exceptions like this one in the system log:
    
    [2/14/17 18:05:12:189 CET] 00000118 EJBWorkflowMa E
    com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean
    doResumeWorkflowEngine CWLLG0594E: An exception occurred while
    initializing the runnable thread. Error: {0}
    
    com.lombardisoftware.component.common.workflow.WorkflowManagerEx
    ception: Next service item is not defined.
     at
    com.lombardisoftware.component.common.workflow.action.ContinueWi
    thEndStateWMAction.getToProcessItemIdFor(ContinueWithEndStateWMA
    ction.java:109)
     at
    com.lombardisoftware.component.common.workflow.action.ContinueWi
    thEndStateWMAction.performAction(ContinueWithEndStateWMAction.ja
    va:84)
     at
    com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
    doResumeWorkflowEngine(EJBWorkflowManagerBean.java:1551)
     at
    com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
    doResumeWorkflowEngine(EJBWorkflowManagerBean.java:709)
     at
    com.lombardisoftware.server.ejb.workflow.EJBWorkflowManagerBean.
    resumeTask(EJBWorkflowManagerBean.java:367)
    
    The user task implementation fails and error handling in the
    process is triggered or, if no error handling logic is part of
    the process model, the process instance is in the failed state.
    
    PRODUCTS AFFECTED
    IBM BPM Advanced
    IBM BPM Standard
    IBM BPM Express
    

Local fix

Problem summary

  • When a user submits the data of a coach by triggering a boundary
    event, the runtime environment applies the data changes to the
    task instance and tries to continue navigating to the heritage
    human service. If multiple browser tabs are used, the data and
    boundary event that the user sends might not match the current
    state on the server.
    

Problem conclusion

  • A fix will be included in IBM BPM V8.5.7 cumulative fix 2017.03
    that ensures that requests sent from the browser to the server
    are accepted only if the service state in the browser matches
    the state on the server.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57437

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-16

  • Closed date

    2017-03-13

  • Last modified date

    2017-03-27

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

Document Information

Modified date:
27 March 2017