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.

Suggest Edit

Tags:

Published May 5, 2017 - Updated May 16, 2017

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.

Visit the Collaboration Center