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 with Pega 7.1.9

SA-37515

Summary



Users have customized Pega API REST service to retrieve and update the case.

They are facing issue when they try to update the case using REST service and are unable to capture the defect in tracer as it works perfectly fine when tracer is been run.

Without the tracer it is throwing 500 internal error.

In logs, user could see ConcurrentModificationException whenever they try to update the case using PUT method.


Error Messages



java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894)
at java.util.HashMap$ValueIterator.next(HashMap.java:922)


Steps to Reproduce

  1. Create REST API service which retrieves the case data in json (GET method).
  2. Try to update the case using the json file in PUT method.


Root Cause



A defect in Pegasystems’ code or rules.

In ClipboardPageImpl.trackAllFirstLevelProperties() replacing iterator with toarray caused the issue.

Resolution



Apply HFix-34205.

Published May 16, 2017 - Updated October 8, 2020

Was this useful?

100% 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