File Size for Asynpool massive


service connect seems to be creating a huge asyncpool on our hard drive why is this we have now moved it will this cause any knock on affects ?

Hi Connor,

The .asyncpool files represent messages in Service Connect’s asynchronous pool.
If you take a look in Service Connect Administration Console - Connectivity - Asynchronous Pools, you can verify that it is the case, since for each async pool this node shows the number of messages in the queue.

The reason for these files appearing is that some entity is posting messages to Service Connect for asynchronous processing.

That may be one of the following:

  1. Another SC workflow that entered an endless loop for some reason and is calling a sub-workflow asynchronously (which resolves to posting into async pool until the message gets processed).

  2. A BPM directive that is attempting to invoke SC workflow asynchronously (and is somehow in an endless loop).

  3. An SC input channel that is either actually receiving many-many files (because something else is posting them) and is set to process messages non-sequentially (i.e. asynchrnonously).

Where to look:

  1. In SC Admin Console, look for the number of messages in Asynchronous Pool queues

  2. In SC Admin Console - Connectivity - Running Workflows look for which workflows are running (they have green icons), and, if a workflow has Document Tracking collected for it, you can right-click it and select View Activity to see what this workflow is doing; also, you can break workflow execution for the selected workflow(s). This may or may not give you a clue as to what is triggering the workflow.

  3. To stop a runaway workflow, you can also just restart ScaDESRouter service on SC server.
    WARNING: This will break the execution of all workflows that are processing messages at that particular moment.

  4. If a message is arriving through input channels, in SC Admin Console - Connectivity - Communication Setup - - Channels – allows you to check how many messages are arrived through which channel. If you have one of the channels showing that number of messages that you see reaching your async pool, by going into inner Input Channels node you can disable this channel and see where it is getting its data from.