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

rxnetty 0.4.20 tcp client #580

Open
gang4 opened this issue Feb 28, 2017 · 0 comments
Open

rxnetty 0.4.20 tcp client #580

gang4 opened this issue Feb 28, 2017 · 0 comments

Comments

@gang4
Copy link

gang4 commented Feb 28, 2017

Here is my issue in rxnetty 0.4.20. In simplest test case, my client writes to my test server, the server just read all buffer, then close the channel (for load test that use pooled tcp connection, we do not see the server, which is a production server, close the connection. But, we still see NoSuchElementException in a rate around 0.0000077). In my client, doOnComplete() in my pipeline is called, but no doOnNext. For the blocking call, client will receive NoSuchElementException. For non blocking call, onComplete is called without onNext. So is there a way to guarantee either (1) onError or (2) onNext and onComplete called, if I know server sends data back?

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

1 participant