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

Websocket error: close 1006 (abnormal closure): unexpected EOF #110

Closed
cyrixsimon opened this issue Jun 10, 2024 · 4 comments
Closed

Websocket error: close 1006 (abnormal closure): unexpected EOF #110

cyrixsimon opened this issue Jun 10, 2024 · 4 comments
Assignees
Labels
bug Unwanted / harmful behavior

Comments

@cyrixsimon
Copy link
Contributor

Hello,

when I query a large dataset with a select, I get a websocket error.

#Rows: 350000000
#Columns: 39

Query
select col1, col2 ... from schema.table

Error
websocket error: close 1006 (abnormal closure): unexpected EOF

@kaklakariada
Copy link
Collaborator

Thank you very much for your bug report! I will ask our product manager to put this and #111 onto the roadmap.

@kaklakariada kaklakariada added the bug Unwanted / harmful behavior label Jun 10, 2024
@kaklakariada kaklakariada self-assigned this Jun 25, 2024
@kaklakariada
Copy link
Collaborator

kaklakariada commented Jun 25, 2024

@cyrixsimon I am trying to reproduce this error. At what point in time do you get this error? in database.Query() or rows.Scan(), i.e. did you already receive data when the error occurred?

In my experiment the driver logs the following while running database.Query():

[exasol] 2024/06/25 09:43:11 websocket.go:125: W-EGOD-17: could not receive data: 'websocket: close 1006 (abnormal closure): unexpected EOF'
[exasol] 2024/06/25 09:43:11 websocket.go:125: W-EGOD-17: could not receive data: 'websocket: close 1006 (abnormal closure): unexpected EOF'

Did you get the same output or a different one?

Which configuration do you use for the connection? Especially fetch size and compression?

Also it would be helpful to know which Exasol version you are using, and the installation type (On prem, Cloud or SaaS).

@cyrixsimon
Copy link
Contributor Author

My analyses have shown that the session is being killed by the database. This case can therefore be cloded, it is an issue on the database. Thanks!

@kaklakariada
Copy link
Collaborator

@cyrixsimon thanks for your reply, great you could solve the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unwanted / harmful behavior
Projects
None yet
Development

No branches or pull requests

2 participants