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

Unexpected DatabaseException errors in log

SA-25565

Summary



Unexpected DatabaseException errors appear in the logs.

Error Messages



**Date and time**,310 [ ajp-bio-8009-exec-8] [TABTHREAD4] [ ] [App:01.01.01] (d_PegaCA_IntentCategory.Action) ERROR localhost |x.x.x.x user-
Unexpected DatabaseException com.pega.pegarules.pub.database.BadClassDefinitionException: Attempting to access a rule with a bad defined-on class:
<blank>

Steps to Reproduce



Launch the Customer Process Manager (CPM) interaction portal.

Root Cause



The error occurs when the Obj-Open in step two of the CPMGetIntentTasksByCategory activity fails.

Resolution



Perform the following local-change:
  1. Save the CPMGetIntentTasksByCategory activity in ruleset.
  2. Add a transition to Step 2 to check if the step failed.
  3. If the step failed, jump to the last step.

Note: The CPMGetIntentTasksByCategory is modified with this change in Pega Customer Service 7.21.

Suggest Edit

Published July 28, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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