Trading Node Disconnects from MetaTrader RPYC API on Client Connection

[seekersoftec]

Problem:

Trading Node appears to lose its connection to the MetaTrader RPYC API when a new client connects to the API. This disrupts the trading process and can lead to unexpected behavior.

Steps to Reproduce:

1. Start Trading Node: Ensure Trading Node is running and connected to the MetaTrader RPYC API.
2. Connect Another Client: Have another client attempt to connect to the MetaTrader RPYC API.
3. Observe Disconnection: Monitor Trading Node's connection to the API. It should disconnect shortly after the new client connects.

Expected Behavior:

Trading Node should maintain its connection to the MetaTrader RPYC API regardless of other clients connecting to the API.

Possible Causes:

• Resource Exhaustion: The MetaTrader RPYC API might be reaching its resource limits when multiple clients connect, causing Trading Node to be disconnected.
• API Limitations: There could be inherent limitations in the MetaTrader RPYC API that prevent multiple clients from connecting simultaneously.
• Trading Node Bug: A bug in Trading Node might be causing it to handle multiple client connections incorrectly.

Additional Information:

• Trading Node Version: Specify the version of Trading Node being used.
• MetaTrader Version: Indicate the version of MetaTrader the RPYC API is connected to.
• Environment: Describe the operating system and any relevant environment variables.
• Logs: If available, include any relevant logs from Trading Node or the MetaTrader RPYC API.

Possible Solutions:

• Increase API Resources: If the API is reaching its limits, consider increasing resource allocation.
• Review API Documentation: Check the MetaTrader RPYC API documentation for any limitations or recommendations regarding multiple client connections.
• Debug Trading Node: If a bug is suspected, examine Trading Node's code to identify and fix the issue.