Resolving Workpoint Exceptions for Inactivated Job Processes

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

Workpoint (WP) exceptions may occur during Identity Manager startup even when job processes have been inactivated and all associated jobs are in a 'Cancelled' state. These exceptions often reference specific script IDs (e.g., Script ID 1:WPDS) and may indicate that legacy monitor records persist in the database, causing the engine to attempt execution of invalid or outdated scripts.

Environment

Identity Manager 14.x

Cause

This issue typically occurs because old records remain in the WP_SCRIPT_MONITOR table. When the Workpoint server initializes, it attempts to process these legacy records, leading to java.lang.ClassNotFoundException or other script execution errors if the associated classes or processes are no longer present or active.

Resolution

Follow these steps to identify and remove the stale monitor records:

1. Analyze Logs: Review the Workpoint monitor logs to locate the specific script error. Look for stack traces that reference the Action Monitor (e.g., Query_actionq#ActionQ1).

2. Query the Database: Connect to the Identity Manager database and query the WP_SCRIPT_MONITOR table to identify records associated with the cancelled jobs.

   • Example Query:

     SELECT * FROM WP_SCRIPT_MONITOR WHERE ...;

3. Delete Stale Records: If the returned records correspond to jobs that are confirmed as cancelled, delete these monitor records from the WP_SCRIPT_MONITOR table.

4. Restart Identity Manager: After removing the stale records, restart the Identity Manager server to allow the Workpoint engine to initialize without attempting to process the removed jobs.

---

Note: Always ensure you have a verified backup of the database before running any manual delete operations against internal tables.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.