You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: