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

Fixed BlockingConnection handling of server-initiated Connection.Close as well as of sudden loss of connection with broker #542

Merged

Conversation

vitaly-krugl
Copy link
Member

Fixed #541 - Make sure connection state is properly reset when BlockingConnection._check_state_on_disconnect raises ConnectionClosed. This supplements the previously-merged PR #450 by getting the connection into consistent state.

Fixed #540 - fix handling of Connection.Close in BlockingConnection._on_connection_closed that was preventing ConnectionClosed from being raised.

Also, together with PR #533, this should address #412

…kingConnection._check_state_on_disconnect raises ConnectionClosed. This supplements the previously-merged PR pika#450 by getting the connection into consistent state.

Fix pika#540 - fix handling of Connection.Close in BlockingConnection._on_connection_closed that was preventing ConnectionClosed from being raised.
@vitaly-krugl vitaly-krugl changed the title Fixed handling of server-initiated Connection.Close as well as of sudden loss of connection with broker Fixed BlockingConnection handling of server-initiated Connection.Close as well as of sudden loss of connection with broker Apr 3, 2015
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 72.52% when pulling 63d2951 on vitaly-krugl:pika540-connectionclosed-on-lost-connection into 409670b on pika:master.

@vitaly-krugl
Copy link
Member Author

Very strange situation with coverall failure here: my test only added about 5 lines of code, so I don't see why it's unhappy.

@gmr
Copy link
Member

gmr commented Apr 13, 2015

Thanks for the PR, I'll take a look ASAP.

…hod() and log ConnectionClosed in BlockingConnection._on_connection_closed()
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.18%) to 72.44% when pulling d11e73f on vitaly-krugl:pika540-connectionclosed-on-lost-connection into 409670b on pika:master.

@gmr
Copy link
Member

gmr commented Apr 29, 2015

LGTM, thanks

gmr added a commit that referenced this pull request Apr 29, 2015
…-lost-connection

Fixed BlockingConnection handling of server-initiated Connection.Close as well as of sudden loss of connection with broker
@gmr gmr merged commit 593dda4 into pika:master Apr 29, 2015
vitaly-krugl referenced this pull request Apr 29, 2015
- Just use the normal check state on disconnect
- Make some methods static
- Avoid redeclaring variables used in module scoped imports
@vitaly-krugl vitaly-krugl deleted the pika540-connectionclosed-on-lost-connection branch May 5, 2015 00:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants