bitshares / bitshares/bitsharesjs-ws

Terminating a ws connection takes forever, why?

Open
#21 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
31
Forks
121
Avg merge
7h 10m
Merged PRs (30d)
1

Description

I am testing new reconnection strategy for UI and I found that it takes forever when ChainWebSocket recognizes that connection is dead until the rpc_connection_status in BlockchainStore is updated.

Why is that @svk31 ? You can test it by simply opening the UI and disabling the internet connection after connection has been established. Are there any timeouts involved that are possibly to high?

![image](https://user-images.githubusercontent.com/33128181/42309257-5a959cb2-8038-11e8-80ec-13166a598679.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue in the UI by disabling internet access after the connection is established. Trace how ChainWebSocket recognizes the dead connection and how BlockchainStore updates rpc_connection_status; done means the status changes promptly after the connection is lost.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.