Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

WS Error <Internal>: Attempting to send a message to closed connection. #6406

Closed
5chdn opened this issue Aug 29, 2017 · 5 comments
Closed

WS Error <Internal>: Attempting to send a message to closed connection. #6406

5chdn opened this issue Aug 29, 2017 · 5 comments
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. P5-sometimesoon 🌲 Issue is worth doing soon.
Milestone
2.3

Comments

@5chdn
Copy link
Contributor

5chdn commented Aug 29, 2017

Before filing a new issue, please provide the following information.

I'm running:

  • Parity version: 1.7.0
  • Operating system: Linux
  • And installed: binaries

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

Probably related to #6387 - when closing the UI, the logs get spammed with 1000's of the following lines:

WS Error <Internal>: Attempting to send a message to closed connection.

It's probably the piled-up RPC responses trying to talk to the close wallet session.
@5chdn 5chdn added F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. labels Aug 29, 2017
@tomusdrw
Copy link
Collaborator

Yup, should the warning be supressed?

@5chdn
Copy link
Contributor Author

5chdn commented Aug 29, 2017

Supressed or better integrated to the parity logging format (with timestamp, log level, colors, etc.).

This was referenced Aug 30, 2017
Closed
Closed
@5chdn 5chdn added the P5-sometimesoon 🌲 Issue is worth doing soon. label Sep 4, 2017
@5chdn 5chdn added this to the 1.9 milestone Oct 5, 2017
@debris
Copy link
Collaborator

debris commented Dec 29, 2017

@tomusdrw is it still an issue?

@tomusdrw
Copy link
Collaborator

Will be fixed by paritytech/jsonrpc#158 in near future, imho no reason to dig into it earlier (it doesn't happen that often now, when UI RPC spam has been fixed).

@5chdn 5chdn modified the milestones: 1.9, 1.10 Jan 23, 2018
@5chdn 5chdn modified the milestones: 1.10, 1.11 Mar 1, 2018
@5chdn 5chdn modified the milestones: 1.11, 1.12 Apr 24, 2018
@folsen
Copy link
Contributor

folsen commented May 19, 2018

@5chdn @tomusdrw does this still happen? Looks like some PRs to jsonrpc in the meantime may have fixed the issue?

@5chdn 5chdn modified the milestones: 2.0, 2.1 Jul 17, 2018
@5chdn 5chdn modified the milestones: 2.1, 2.2 Sep 11, 2018
@5chdn 5chdn modified the milestones: 2.2, 2.3 Oct 29, 2018
@folsen folsen closed this as completed Nov 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. P5-sometimesoon 🌲 Issue is worth doing soon.
Projects
None yet
Milestone
2.3
Development

No branches or pull requests
4 participants
@folsen @tomusdrw @debris @5chdn