question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unexpected exception raised in websocket.

See original GitHub issue

I am running hasura/graphql-engine:v1.3.1 docker image on an ec2 t2.medium instance. Sometime i encounter sequence of following errors in the logs. I am using apollo client for subscriptions.

{"type":"unstructured","timestamp":"2020-10-19T14:41:01.279+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"} {"type":"unstructured","timestamp":"2020-10-19T14:43:36.701+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"} {"type":"unstructured","timestamp":"2020-10-19T14:44:31.333+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"} {"type":"unstructured","timestamp":"2020-10-19T14:45:01.085+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"} {"type":"unstructured","timestamp":"2020-10-19T14:48:00.665+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"} {"type":"unstructured","timestamp":"2020-10-19T14:48:00.665+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"} {"type":"unstructured","timestamp":"2020-10-19T14:51:01.300+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"}

Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:7 (1 by maintainers)

github_iconTop GitHub Comments

6reactions
24601commented, May 12, 2022

This continues to be an issue for us. In this day and age, 5MB of data is “not that much” and a system really should not croak on it. If PG can handle it, the graphql-engine on top of it should. Graphql-engine should not impose limitations on size that are smaller than those handled by PG/underlying DB…that seems anathema to the whole point of the engine…

Even so, killing the thread (which borks tons of other stuff) is not a great way to handle this even if this limitation exists…

Happens as recently as 2.6.2.

#6542 seems to have same issue.

0reactions
karibertilscommented, Jan 30, 2022
{"type":"unstructured","timestamp":"2022-01-30T15:56:58.584+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T15:56:58.584+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T15:56:58.584+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T15:56:58.584+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T15:56:58.584+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T15:56:58.584+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:10:54.411+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:10:54.411+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:12:36.807+0000","level":"warn","detail":"Overdue for a major GC: forcing one even though we don't appear to be idle"}

Also

{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Thread killed by timeout manager"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}
{"type":"unstructured","timestamp":"2022-01-30T16:18:35.944+0000","level":"error","detail":"Unexpected exception raised in websocket. Please report this as a bug: Warp: Client closed connection prematurely"}

Getting this all the time. I’m running hasura/graphql-engine:v2.1.1

Currently, I have a configuration where this happens every time with graphql engine running for like 2-3 minutes. Seems to be somehow related to the clients which have active subscriptions.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unexpected exception trying to send to websocket: code = 1006
Hello everyone, today after updating the Chia GUI to 1.1.7 version (Windows 10 Pro x64) I faced a lot (hundreds) of this kind...
Read more >
WebSocket connection failed: Error during ... - Stack Overflow
I am trying to integrate Socket.io with Angular and I'm having difficulties making a connection from the client-side to the server. I've looked ......
Read more >
977020 - websocket send raises uncaught exception
Error logs indicate that many times uncaught exceptions will be fired. The code sending data to the WebSocket is surrounded by a try-catch, ......
Read more >
websockets.exceptions — websockets 8.1 documentation
:mod:`websockets.exceptions` defines the following exception hierarchy: ... 1010: "extension required", 1011: "unexpected error", 1015: "TLS failure ...
Read more >
WebSockets - Handling Errors
The event onerror is followed by a connection termination, which is a close event. A good practice is to always inform the user...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found