When your workflow template is based on the FCFWorkflow template that is provided with SAS Anti-Money Laundering, you might encounter issues with SAS Workflow Services and Apache ActiveMQ. For example, you might see one or more of the following problems:

• The ActiveMQ log file shows that the WorkflowEventsQueue is at 100% capacity. 
• The number of logs that reside in the SAS-configuration-file\Lev1\Web\activemq\data\kahadb directory grows over time, causing disk space to fill up.
• Transitions between workflow tasks take longer than expected and worsen over time. SAS Workflow Services might eventually become unresponsive.

When the problem occurs, you might see an error similar to the following in the SASWorkflowServices9.4.log file:

The problem is likely caused by policy and design issues in the workflow template. The issues result in a large number of policies that fill up the event queue. Details about the issues are as follows:

1. When the CASE__X_RR_COMPLETE_FLG data object is updated, the root-level policy, Data Object Updated->Copy Data Object->CASE.X_RR_COMPLETE_FLG, copies the value of the data object to itself. This copy action generates another invocation of the same policy. As a result, the data object is updated continuously in an endless loop. . 

To fix the problem, remove this policy from your workflow template.

2. The Wait for Report Acceptance task contains a policy to add the Wait status to the task when the task starts. If the value of the CASE__X_RR_COMPLETE_FLG is not TRUE, then the Report Filed? decision gateway returns the case to the Wait for Report Acceptance task. The workflow loops continuously between the task and the decision gateway until the CASE.X_RR_COMPLETE_FLG is set to TRUE.

To fix the problem, perform the following steps:

• Remove the policy that adds the Wait status to the Wait for Report Acceptance task when the task starts.
• Add a root-level policy to trigger the Wait status update when the CASE.X_RR_COMPLETE_FLG is updated. If the value of CASE.X_RR_COMPLETE_FLG is set to FALSE, the Report Filed? decision gateway returns the case to the Wait for Report Acceptance task. The task waits until the data object is updated again, which triggers the Wait status update policy. If the value of CASE.X_RR_COMPLETE_FLG is set to TRUE, the Report Filed? decision gateway moves the case to the Set Disposition after Report Accepted task. The recommended policy is shown below:

Click the Downloads tab in this note to access a revised FCFWorkflow template containing these corrections.

After you make the recommended changes and activate the corrected workflow template, you should terminate all active workflow instances based on template versions that contain these issues. You also might need to clean up disk space. Follow the instructions in SAS KB0036267, "Increasing numbers of Apache ActiveMQ journal log files in certain SAS® 9.4 Enterprise BI and SAS® Visual Analytics environments fill up disk space."

Note: You might encounter a similar issue with a workflow template that is not based on the FCFWorkflow template or one that is used with a different SAS® solution. If you encounter the issue with a different workflow template, please report the problem to SAS Technical Support. A Technical Support consultant can review your workflow template for similar inefficient logic.

Operating System and Release Information