Connecting to Gateways

The Active Console connects to all Gateways simultaneously. This event gives significant load to the Active Console because it processes the XPaths or data items from those Gateways. When the console is overloaded, it either stops or slows down the processing of data items. This in turn triggers the other Gateways' heartbeat timeout (75 seconds) and disconnects the Active Console.

Solution

There are several ways to solve the said disconnections:

Solution 1

Remove or refactor the List Views that contain non-identifying predicates. The detailed steps can be seen in this FAQ.

Solution 2

If the above does not work, then add the -queueConnections flag to the ActiveConsole.gci file. This instructs the Active Console to connect to the Gateways one-by-one. Here are the steps:

1. Shut down the Active Console.
2. Open the ActiveConsole.gci file using a text editor. The file is located in the same folder as the ActiveConsole.exe file.
3. Add the -queueConnections flag at the end of the file. Make sure that there are no leading or trailing spaces.
4. Save the changes.
5. Start the Active Console.

Reference

• Managing Load in Active Console
• Refactor List Views that contain non-identifying predicates