Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate why numerous websocket connections are open #240

Open
jimmychu0807 opened this issue Mar 5, 2022 · 1 comment
Open

Investigate why numerous websocket connections are open #240

jimmychu0807 opened this issue Mar 5, 2022 · 1 comment
Assignees

Comments

@jimmychu0807
Copy link
Owner

Investigate why there are 3 ws connections opened when connecting to a Substrate node.

@MohammadAbuzar945
Copy link

There could be a few different reasons why this is happening, depending on the specific setup and configuration of your Substrate node and the tools you are using to connect to it.

One possibility is that you are using a tool or library that automatically establishes multiple WebSocket connections to the Substrate node for various purposes. For example, some tools or libraries may establish multiple connections to improve performance, provide redundancy, or support certain features.

Another possibility is that you have configured your Substrate node to allow multiple WebSocket connections from the same client. Some Substrate nodes may be configured to allow multiple connections from the same client in order to support certain scenarios or functionality.

To investigate the cause of this behavior further, you may want to try the following steps:

Check the documentation for the tool or library you are using to connect to the Substrate node. It may provide information on how many WebSocket connections it establishes and why.

Check the configuration of your Substrate node. You can use the system.describe_chain method to retrieve information about the configuration of your node, including the maximum number of WebSocket connections allowed from the same client.

Check the logs of your Substrate node for any messages related to WebSocket connections. These logs may provide additional information on the connections being established and why.

By following these steps, you may be able to identify the cause of the behavior you are observing and understand why three WebSocket connections are being established when you connect to your Substrate node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants