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

PRRuntimeException occurs while updating status

SA-64066

Summary



PRRuntimeException is generated in the Pega log file when updating the status.


Error Messages



com.pega.pegarules.pub.PRRuntimeException: exception with pzmapcases
    at com.pegarules.generated.activity.ra_action_pzloadcasehierarchywrapper_88619a41ce1580fb363f6553a6198739.step5_circum0(ra_action_pzloadcasehierarchywrapper_88619a41ce1580fb363f6553a6198739.java:517)
    at com.pegarules.generated.activity.ra_action_pzloadcasehierarchywrapper_88619a41ce1580fb363f6553a6198739.perform(ra_action_pzloadcasehierarchywrapper_88619a41ce1580fb363f6553a6198739.java:150)
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3527)

Caused by: org.postgresql.util.PSQLException: This connection has been closed.
    at org.postgresql.jdbc.PgConnection.checkClosed(PgConnection.java:766)
    at org.postgresql.jdbc.PgConnection.getAutoCommit(PgConnection.java:727)
    at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)



Steps to Reproduce



Unknown


Root Cause



The exception occurred due to PSQLException. This occurred when the application server maintained stale connections and performed a handover to Pega to commit the work objects.


Resolution



Perform the following local-change to avoid stale connections:

Set the WebSphere Application Server (WAS) to verify if the connection is still valid. The steps depends on the version of the WAS.

Perform the below steps for WebSphere Application Server (WAS) 8:
  1. In the WebSphere Administrator Console, navigate to Resources > JDBC > Data Sources.
  2. On the Data Sources page, navigate to <name of the Pega data source>.
  3. On the Pega Data Source page, Navigate to WebSphere Application Server data source properties.
  4. In the Connection Validation Properties, select the following options,
    Validate new connections
    Validate existing pooled connections
  5. In the Validation Options, enter a query,
    Use 'SELECT * FROM DUAL' by default. 

    This query runs in a constant time.
For more information, refer to: https://community.pega.com/support/support-articles/caught-exception-during-autocommit-check-error-broken-queue

Published February 16, 2019 - 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