Hello All,
I have a fulfillment workflow which generally runs fine however, in rare cases it just hangs which out any feedback.
My hunch is that is an issue with the data being passed to it, however, I'm at stumps as to how to diagnose and locate the root cause.
Not sure if there is an easier way to find the root cause. I switched on debug mode and trawled through 1000's of lines of output to get to the stacktace. As suspected, there was a mandatory data value missing causing it to hang.
Is there a better way to deal with this? and detect the issue?
Can you share the error you saw in the logs?
Hi Boris,
Hope you had a enjoyable new year! Here is a snipped of a very long stacktrace.
As you can see that there is a missing value for required for parameter 'givenName'.
01/05/2017 15:53:20.450 ERROR (Worker_actionq#ActionQ1#WPDS_206) [com.aveksa.afx.plugin.integration.fulfillment.validation.FulfillmentRequestValidator]
com.aveksa.afx.plugin.integration.fulfillment.validation.InvalidParameterValueException: Missing value for required parameter 'givenName'
at com.aveksa.afx.plugin.integration.fulfillment.validation.ParameterValidationUtil.validateRequired(ParameterValidationUtil.java:88)
at com.aveksa.afx.plugin.integration.fulfillment.validation.ParameterValidationUtil.validateRequired(ParameterValidationUtil.java:69)
at com.aveksa.afx.plugin.integration.fulfillment.validation.ParameterValidationUtil.validate(ParameterValidationUtil.java:24)
at com.aveksa.afx.plugin.integration.fulfillment.validation.FulfillmentRequestValidator.validate(FulfillmentRequestValidator.java:77)
at com.aveksa.afx.plugin.service.AFXFulfillmentServiceProvider.insertFulfillmentRequest(AFXFulfillmentServiceProvider.java:462)
at com.aveksa.afx.plugin.service.AFXFulfillmentServiceProvider.queueAfxCommand(AFXFulfillmentServiceProvider.java:96)
at com.aveksa.server.workflow.scripts.nodes.ProvisioningCommandNode.nodeAvailableAsynchronous(ProvisioningCommandNode.java:102)
at com.aveksa.server.workflow.scripts.nodes.WorkflowNodeHandler.nodeAvailableAsynchronous(WorkflowNodeHandler.java:54)
You don't say what version and patch level you are on. There is a known issue with some patches where the workflow does not correctly handle some error status from AFX.
See the following article:
Hello Ian
I did see this articile also while doing some digging, but could not relate to the extact behaviour.
I'm on patch level 7.0.0.101393 P01
Andrew
the 7.0.0 P01 version you are on is susceptible to this problem and it is not resolved unless you patch to 7.0.0 P04 or later. If you see the AFX status "Workflow flagged as stalled based on stall detection settings" then you most likely are seeing this issue or a related issue. Note that this problem with the workflow stalling only occurs when there is a failure of AFX to complete the provisioning. Your comments seem to suggest that AFX was failing due to a missing parameter. If this was the case, I would expect the Workflow to fail in the manner described. The fix described in the article only allows the workflow complete, if AFX failed this usually means the workflow proceeds to a manual fulfillment node.
You can of course always resolve this issue by resolving the underlying AFX problem. If AFX does not fail then your workflow will succeed.
Thanks Ian.
I will keep a close eye on it. I do have plans to update to the latest service pack but this is a big task which requires a lot of testing before I can proceed.
Have you verified that you have the "Wait for result" turned on???
Yes of course. That was one of my pre-checks.
Thanks Ian.
I will keep a close eye on it. I do have plans to update to the latest service pack but this is a big task which requires a lot of testing before I can proceed.