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

ERROR:tornado.application:Uncaught exception POST /events (127.0.0.1) #934

Open
linnuo520 opened this issue May 16, 2024 · 0 comments
Open

Comments

@linnuo520
Copy link

I have recently encountered an issue while using Visdom for data visualization, specifically receiving frequent WebSocketClosedError errors when attempting to send data to the client via WebSocket. The problem seems to arise when attempting to write a message to the WebSocket connection, only to find that the connection has already been closed. The detailed error trace is as follows:

image Given this context, I have several inquiries seeking your assistance:

Are there known scenarios or configuration issues that could lead to unexpected closure of WebSocket connections during data transmission?
Are there any recommended best practices or configuration adjustments to enhance the stability of WebSocket connections?

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

1 participant