Avoiding resource pending configurations

Avoid configuring maps that can cause them to become "Resource Pending".

The Launcher prepares maps for execution through a two step process. The following is a simplified discussion of the process. For a detailed discussion, refer to the Launcher documentation.

Step 1: Allocates a thread for a map/trigger file combination. Map/trigger file combinations that fail to fulfill the requirements to successfully allocate a thread get placed on hold with a status of "Init Pending".

Step 2: Maps/trigger file combinations that have a thread allocated will then be executed unless they fail resource requirements. Such combinations will be placed on hold with a status of "Resource Pending".

The Launcher is configured with a finite number of threads to execute maps (either Message Manager maps and/or your own maps). If a map becomes Resource Pending (for example, if multiple instances of it append to a single file), it prevents other maps from using that thread. Multiple instances of the same map, except for the one that owns the resource in a Resource Pending state will, in effect, stall the Launcher's processing capabilities down to the one map that owns the resource. If this occurs, it is better to configure that map so that it becomes Init Pending before it can become Resource Pending, and therefore allow other maps to use the available thread.