-
Notifications
You must be signed in to change notification settings - Fork 184
On error not triggered when listen connection terminated #212
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
Labels
type: bug
A general bug
Milestone
Comments
Probably it would make sense to send different signals when the connection was closed intentionally and unintentionally. If the server goes down, we should send |
mp911de
added a commit
that referenced
this issue
Jan 20, 2020
We now terminate the notification stream (PostgresqlConnection.getNotifications()) when the connection gets disconnected. If the connection is closed normally, the stream terminates successfully (onComplete). Unintended disconnects result in an error (onError). [#212]
gregturn
pushed a commit
that referenced
this issue
Jan 27, 2020
We now terminate the notification stream (PostgresqlConnection.getNotifications()) when the connection gets disconnected. If the connection is closed normally, the stream terminates successfully (onComplete). Unintended disconnects result in an error (onError). [#212]
mp911de
added a commit
that referenced
this issue
Jan 28, 2020
We now terminate the notification stream (PostgresqlConnection.getNotifications()) when the connection gets disconnected. If the connection is closed normally, the stream terminates successfully (onComplete). Unintended disconnects result in an error (onError). [#212]
mp911de
added a commit
that referenced
this issue
Jan 28, 2020
mp911de
added a commit
that referenced
this issue
Jan 28, 2020
We now terminate the notification stream (PostgresqlConnection.getNotifications()) when the connection gets disconnected. If the connection is closed normally, the stream terminates successfully (onComplete). Unintended disconnects result in an error (onError). [#212]
That's fixed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Fails to trigger an
onError
when the database is stopped and using postgresql listen.Versions
0.8.0.RELEASE
postgres:11.3-alpine
Current Behavior
Stack trace
Table schema
Input Code
-- your SQL here;
Steps to reproduce
Run JUnit test:
R2dbcListenApplicationTests.testDisconnect()
:https://github.com/steven-sheehy/r2dbc-listen
Input Code
// your code here;
Expected behavior/code
Possible Solution
Additional context
The text was updated successfully, but these errors were encountered: