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

DSM ISRuntimeException and ConstraintViolationException



User organization receives 200K+ account updates each night. We have file listeners that create System-Queue- records and queues each account update to be updated by background agents. During the processing of these queue items, 1 or more strategies are executed to determine a communication option for the account owner.

While running these account updates and strategies each night, we end up with a small number that become Broken-Process due to ISRuntimeExceptions. There is nothing in the queue record that describes what the issue is. Including log files from Interaction Services application and samples of the broken-queue records.

Error Messages

** Java Exception: java.lang.RuntimeException: java.lang.RuntimeException: org.hibernate.exception.ConstraintViolationException: could not insert: []

** Java Exception: java.lang.RuntimeException: java.lang.RuntimeException:

Steps to Reproduce

After the agents have completed processing all the queue items, check out the Broken Process view.

Root Cause

The data which is getting stored as the interaction result was not unique by account. In the files being processed, the "key" fields were seen in multiple accounts. 


Advised user to remove the custom logic causing this issue and they will add new code changes to handle this in a better fashion

Published January 31, 2016 - 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