Cooperative file listening and fault tolerance

With cooperative file listening, source-event files are retained when a Launcher or a map fails.

When a Launcher fails and cooperative file listening is enabled, the File adapter automatically saves the source-event files of the failed Launcher. Other Launchers continue to process source-event files as they arrive, so the failure of one or more Launchers or maps causes minimal processing delays.

The File adapter saves the source-event files of the failed Launcher in a subdirectory of the trigger directory. The subdirectory is WTX_port_num_hostname, where port_num and hostname are the control port and host name of the Launcher.

When the failed Launcher restarts, the File adapter automatically returns the Launcher’s source-event files to the trigger directory, where any Launcher that is listening can process them.

If the failed Launcher cannot restart, you can manually move its source-event files to the trigger directory.

When a map fails and cooperative file listening is enabled, the File adapter automatically saves the source-event files to an error directory. You can use the error directory as the trigger directory for an error-processing map.

File listener messages are logged in the Launcher log file.