Support Article

Unexpected DatabaseException errors in log



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 Attempting to access a rule with a bad defined-on class:

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.


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.

Published July 13, 2016 - Updated July 27, 2016

Have a question? Get answers now.

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