IBM Support

JR47535: CONCURRENTMODIFICATIONEXCEPTION WHEN USING BPM REST API AND TRACING IS ENABLED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When querying services via BPM REST API and when trace is
    enabled this can lead to an ConcurrentModificationException
    when the underlying execution continues.
    

Local fix

  • Disabling trace
    

Problem summary

  • When retrieving services via BPM REST API the execution context
    will retrieved.  If the execution context will be updated by
    the BPD engine while the execution context is used by the BPM
    REST API this can lead to the exception due to missing
    synchronization on the execution context.
    
    
    PROBLEM DETAILED DESCRIPTION:
    When using the BPM REST API to retrieve services this can lead
    to an ConcurrentModificationException similar to this:
    
    java.util.ConcurrentModificationException
    at java.util.AbstractList$SimpleListIterator.next
      (AbstractList.java:64)
    at com.lombardisoftware.component.common.workflow.
      ExecutionContext.toString(ExecutionContext.java:1053)
    at java.lang.String.valueOf(String.java:1528)
    at java.lang.StringBuilder.append(StringBuilder.java:194)
    at java.util.AbstractMap.toString(AbstractMap.java:618)
    at java.lang.String.valueOf(String.java:1528)
    at com.ibm.bpm.rest.impl.service.ServiceRunnerManager.
      initOldWebWFM(ServiceRunnerManager.java:101)
    at com.ibm.bpm.rest.impl.service.ServiceRunnerManager.
      getInstance(ServiceRunnerManager.java:66)
    at com.ibm.bpm.rest.impl.service.ServiceResource.
      getServiceActions(ServiceResource.java:105)
    

Problem conclusion

  • With this interim fix the synchronization between different
    threads will be fixed so that access to the exection context by
    multiple threads is possible.
    
    FIX AVAILABILITY:
    iFix for 7.5.1.1 is available on Fix Central, search for APAR
    JR47535 at http://www.ibm.com/support/fixcentral/
    Fix is also targetted for inclusion in next fixpack for BPM
    V7.5.1, BPM 8.0.1, BPM 8.5.0
    
    When obtaining any of the above fixes, be sure to download the
    accompanying readme, for itself, and any prerequisite fixes, and
    review them thorougly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR47535

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-08-16

  • Closed date

    2013-11-20

  • Last modified date

    2013-11-20

  • 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

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

Document Information

Modified date:
20 November 2013