Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Concurrent modification exception

SA-64199

Summary



ConcurrentModificationException occurs in the REST Service activity.


Error Messages



java.lang.Thread.run(Thread.java:748) [?:1.8.0_131];Caused by: java.util.ConcurrentModificationException; at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437) ~[?:1.8.0_131]; at java.util.HashMap$KeyIterator.next(HashMap.java:1461) ~[?:1.8.0_131]; at java.util.AbstractCollection.addAll(AbstractCollection.java:343) ~[?:1.8.0_131]; at java.util.HashSet.<init>(HashSet.java:119) ~[?:1.8.0_131];


Steps to Reproduce

  1. Create a REST service to obtain additional details for the work objects.
  2. In the Service activity, invoke the Apply data transform.
  3. In data transform, update the work object page.
  4. Autopopulate one of the properties from the node level data page by Refer to Option.


Root Cause



The issue occurred due to the known limitation of the node level data page copy. Node level pages are not thread-safe. Hence, ConcurrentModification exception occurs when multiple thread-level pages 'refer' to instead of 'copy' from.

Resolution



Perform the following local-change:

Change Data access to 'Copy data from a data page' instead of 'Refer to a data page'.

Published October 10, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us