Workpoint exceptions | Now showing up in 14.4 CP1 logs
search cancel

Workpoint exceptions | Now showing up in 14.4 CP1 logs

book

Article ID: 235320

calendar_today

Updated On:

Products

CA Identity Manager

Issue/Introduction

We just upgraded IDM in PROD to 14.4 CP1.

We are seeing multiple exceptions showing up on the logs that are related to old processes/jobs. IDM is working fine, existing and new workpoint jobs are also behaving fine.

2022-02-05 22:13:46,829 [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR com.workpoint.server.script.ScriptEngine  - A script error has occurred. Error occurred in Statement #1 in Script ID 1:WPDS, Script Name = '########', Script type = 'Delay Condition'
java.lang.ClassNotFoundException: gov.cdc.sams.workflowscripts.SAMSWorkflowScripts
 at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
 at com.workpoint.server.ServerProperties.getClass(Unknown Source)
 at com.workpoint.server.script.StatementEngineJava.execute(Unknown Source)
 at com.workpoint.server.script.ScriptEngine.A(Unknown Source)

...

2022-02-05 22:13:46,829 [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN  com.workpoint.client.ClientContext  - An error occurred attempting to get the resource name for id='####' using detailScriptID=1:WPDS. WIll display the raw ID instead. Error was: com.workpoint.common.exception.WpServiceException: java.lang.ClassNotFoundException: ########### Error occurred in Statement #1 in Script ID 1:WPDS, Script Name = '##########', Script type = 'Delay Condition'
2022-02-05 22:13:46,845 [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR com.workpoint.server.script.ScriptEngine  - A script error has occurred. Error occurred in Statement #1 in Script ID 1:WPDS, Script Name = '##########', Script type = 'Delay Condition'
java.lang.ClassNotFoundException: ########

Old processes/jobs data was present earlier with IDM version 14.2, but above exceptions were not present in the 14.2 logs.

Those jobs/processes are no longer needed.

Would below cleanup tasks be a feasible solution?

* Archive the old process and associated jobs using Designer "Export" feature.

* Delete the old process and associated jobs using Designer "Delete" feature.

 

Environment

Release : 14.4

Component : IdentityMinder(Identity Manager)

Resolution

Yes. Please remember, there is no Bulk delete feature, you will have to click on each job and then choose delete.