Skip to content

Update dependencies, cleanup RSocketClient/Server implementation #466

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

Merged
merged 4 commits into from
Feb 2, 2018

Conversation

rdegnan
Copy link
Member

@rdegnan rdegnan commented Feb 1, 2018

Merge some changes from JCTools, clean up a few places where synchronization is no longer needed after switching to NonBlockingHashMapLong

@rdegnan rdegnan requested a review from robertroeser February 1, 2018 05:21
@@ -64,16 +52,16 @@ public NettyDuplexConnection(NettyInbound in, NettyOutbound out, NettyContext co

@Override
public void dispose() {
onClose.onComplete();
context.dispose();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This didn't seem to work reliably. Did this get fixed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the dispose part worked, the problem was the onClose callback not getting triggered when the process is forcibly killed, so this should be no worse than it is now. The real problem is that there are two sources of truth, the underlying channel and Netty's CloseFuture which seem to not always be in agreement. I'd like to add some tests to try to reproduce this, then see if there is a better way of making sure the CloseFuture always gets terminated.

@robertroeser robertroeser merged commit 30d3cf2 into rsocket:1.0.x Feb 2, 2018
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

Successfully merging this pull request may close these issues.

3 participants