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.

Sign up for GitHub

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

Jump to bottom

Reconnecting WebSocketService after a close call #1356

Closed
dfsantamaria opened this issue Jan 29, 2021 · 0 comments · Fixed by #1645
Closed

Reconnecting WebSocketService after a close call #1356

dfsantamaria opened this issue Jan 29, 2021 · 0 comments · Fixed by #1645
Labels
needs-review issue/PR needs review from maintainer

Comments

@dfsantamaria
Copy link

dfsantamaria commented Jan 29, 2021 •
edited

I'm wondering how to reconnect a WebSocketService after a close (specifically, after a WebSocketNotConnectedException exception is thrown) without re-instantiating the WebSocketService object and the related Web3j object and contract.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-review issue/PR needs review from maintainer
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix reconnect on refused connection zilm13/web3j
1 participant
@dfsantamaria