Oleh Dokuka
Oleh Dokuka
just a link to another example which shows the need for this feature (see #1039)
@mkrzywanski can your try to add to your main method a line with `Hooks.onOperatorDebug` to see the full stack trace of the exception
@mkrzywanski Also, can you try to reproduce the same just with a pure rsocket to reduce the problem surface?
@sdack-cloud which rsocket version are you using? Can you also prepare a small application that can reproduce that in an isolated environment? Also, it is unclear what is the server...
KeepAlieve is an important part of the connection failure diagnosis that we have in RSocket. Thus JavaDocs says to enable it and have a meaningful ping period and the timeout...
@linux-china @marcambier and others, would you like to make a contribution?
now this PR should be relevant
@jGleitz there is a workaround as of now which is replacement of `publish` with `replay(history=0)`.
```java Disposable d = Mono.fromFuture(future) // source is fn .flatMap() // flat map can not fuse since the source is just push based observable .subscribe(); // 5 sec wait d.dispose()...
fixed by #3557