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

SLA Agent entries go to broken-queue on Decision Hub with error

SA-61699

Summary



SLA Agent entries go to the broken-queue on Decision Hub node with an error.


Error Messages



Queue error details in XML of the broken tem:

Trying to save an invalid page: ** ** java.lang.NoClassDefFoundError: com/pega/pegarules/priv/alert/AlertBuildContext$ParameterPageFilterType
Trying to save an invalid page: page is not valid</pxErrorMessage>

Trying to save an invalid page: ** ** java.lang.NoClassDefFoundError: com/pega/pegarules/priv/alert/AlertBuildContext$ParameterPageFilterType
Trying to save an invalid page: page is not valid



Steps to Reproduce



Log in to System Management Application (SMA) and observe the behavior.


Root Cause



A defect or configuration issue in the operating environment. 

The issue is with an extension 'plv8' of Postgres 9.4.17. Error occurs when there are User Defined Functions (UDF’s) used in the SQL statements and Postgres encounters a segmentation fault terminating one of the critical process in the database server. 

Resolution



Make the following change to the operating environment:

Replace Postgres 9.4.1.7 with Postgres 9.4.1.5 or 9.4.18.

Published August 24, 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