AnsweredAssumed Answered

Requests not processed

Question asked by Bas Rozemond on Feb 25, 2020
Latest reply on Feb 27, 2020 by Ian Staines

Like • Show 0 Likes0
Comment • 4

New requests aren't processed and remain in the open state. I think the following error message has something to do with it.

Does anybody have a suggestion?

com.aveksa.server.core.AdminServiceException: com.aveksa.server.core.AdminServiceException: com.aveksa.server.workflow.WorkflowServiceException: Error creating a running instance of the process definition 324
at com.aveksa.server.core.cr.concurrent.WFCreationTask.call(WFCreationTask.java:111)
at com.aveksa.server.core.cr.concurrent.WFCreationTask.call(WFCreationTask.java:35)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.aveksa.server.core.AdminServiceException: com.aveksa.server.workflow.WorkflowServiceException: Error creating a running instance of the process definition 324
at com.aveksa.server.core.cr.concurrent.WFCreationTask.call(WFCreationTask.java:90)
... 5 more
Caused by: com.aveksa.server.workflow.WorkflowServiceException: Error creating a running instance of the process definition 324
at com.aveksa.server.core.cr.concurrent.WFCreationTask.createWorkflow(WFCreationTask.java:196)
at com.aveksa.server.core.cr.concurrent.WFCreationTask.call(WFCreationTask.java:88)
... 5 more
Caused by: java.lang.NullPointerException
at com.aveksa.server.workflow.scripts.nodes.WorkflowNodeHandler.isJobComplete(WorkflowNodeHandler.java:208)
at com.aveksa.server.workflow.RetryEnabledOperationsJobUtils.executeJobStrategyWithProcessing(RetryEnabledOperationsJobUtils.java:214)
at com.aveksa.server.workflow.RetryEnabledOperationsJobUtils.saveWithProcessing(RetryEnabledOperationsJobUtils.java:112)
at com.aveksa.server.core.cr.concurrent.WFCreationTask.createWorkflow(WFCreationTask.java:147)
... 6 more

Ian Staines

Feb 27, 2020 11:15 AM

Correct Answer

Bas,

I recommend you open an RSA Customer Support case for this issue. This kind of general WorkPoint failure is difficult to troubleshoot and requires a hands on approach. When WorkPoint is not processing requests this will generate a huge volume of ERROR messages and it is not easy to determine which messages related to a cause and which are just symptoms of the failure.

See the reply in context

No one else had this question

Outcomes

4 Replies

Ian Staines Feb 25, 2020 12:49 PM
Mark Correct
Correct Answer
This message is seen in systems that are experiencing WorkPoint problems but I suspect it is a symptom of the fact that WorkPoint is not working correctly and does not provide information on what might be causing the problem.
Like • Show 0 Likes0
Actions
- Bas Rozemond @ Ian Staines on Feb 26, 2020 5:24 AM
  Mark Correct
  Correct Answer
  They are probably WP related. Is there a way to get more information? Or some way to restart WP or so?
  Like • Show 0 Likes0
  Actions
  - Azam Muhamad @ Bas Rozemond on Feb 26, 2020 9:20 PM
    Mark Correct
    Correct Answer
    Could you confirm your RSA IGL version. This seems matches with the following issue that is fixed in 7.1.0 P05(see below 7.1.0 P05 Release Note).
    Like • Show 0 Likes0
    Actions
Ian Staines Feb 27, 2020 11:15 AM
Unmark Correct
Correct Answer
Bas,

I recommend you open an RSA Customer Support case for this issue. This kind of general WorkPoint failure is difficult to troubleshoot and requires a hands on approach. When WorkPoint is not processing requests this will generate a huge volume of ERROR messages and it is not easy to determine which messages related to a cause and which are just symptoms of the failure.
Like • Show 0 Likes0
Actions

Requests not processed

Outcomes

Related Content

Recommended Content