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
When the client is closed, the rsocket server does not receive the cancellation event and ongoing flux subscription still continues which leads to data loss.
How to cancel the ongoing subscription in server side when client is closed ?
Expected Behavior
If the client closes then server should also close all the active subscription for that client to prevent data loss.
Actual Behavior
If the client closes then server is not closing the active subscription. And if the flux is never ending, it leads to data loss.
Here is how I created the RSocketRequestor Bean in client side:
Hi, I have new to rsocket, not sure how to handle the above scenario. If there is any workaround to handle the above scenario, could you please help me ?
The text was updated successfully, but these errors were encountered:
When the client is closed, the rsocket server does not receive the cancellation event and ongoing flux subscription still continues which leads to data loss.
How to cancel the ongoing subscription in server side when client is closed ?
Expected Behavior
If the client closes then server should also close all the active subscription for that client to prevent data loss.
Actual Behavior
If the client closes then server is not closing the active subscription. And if the flux is never ending, it leads to data loss.
Here is how I created the RSocketRequestor Bean in client side:
RSocket version(s) used: 1.1.3
Netty version: 4.1.93.Final
JAVA version: 17
Hi, I have new to rsocket, not sure how to handle the above scenario. If there is any workaround to handle the above scenario, could you please help me ?
The text was updated successfully, but these errors were encountered: