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
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.