Closed lexs closed 7 years ago
I think this might be the same issue as https://github.com/ReactiveSocket/reactivesocket-java/issues/169
It is being sent, but client still processes the close first. See https://github.com/rsocket/rsocket-java/issues/311
Throwing SetupException in the handler doesn't seem to do anything, it simple gets swallowed. Same if you receive any frame that isn't SETUP in DefaultReactiveSocketServer. It logs a netty error to the console but doesn't send any frames.