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

Detecting connection closed when pulling changes #164

Open
vlobanov opened this issue May 15, 2016 · 1 comment
Open

Detecting connection closed when pulling changes #164

vlobanov opened this issue May 15, 2016 · 1 comment

Comments

@vlobanov
Copy link

Hello,

I'm trying to use changes query, and problem is that if I start pulling, e.g.

(-> (r/db "test")
    (r/table "messages")
    r/changes
    (r/run conn)
    first)

And then shut down DB server, I never get an exception. It just hangs forever.
Java driver had the same issue, but as far as I can see their solution (re-throw all exceptions) is not applicable in the case.

I didn't see any ping messages protocol, so maybe it's hard or impossible to detect network issues, but when RethinkDB is just shut down and closes connection, that should be possible to detect, right?

I could check periodically if connection is still open as a workaround, but maybe there is a better way?

@apa512
Copy link
Owner

apa512 commented May 15, 2016

Netty is making me extremely confused but it's probably fixable somehow.

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

2 participants