Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Resume working for connection but not a stream

See original GitHub issue

Reproducible with the rsocket-cli project

./rsocket-cli --resume --server -i @/usr/share/dict/words ws://localhost:5001
socat -d TCP-LISTEN:5000,fork,reuseaddr TCP:localhost:5001
./rsocket-cli -i Obama --debug --stream --resume ws://localhost:5000

kill and restart socat

agamogenesis
agamogenetic
agamogenetically
agamogony
16:19:15.491	client Inner connection disconnected: ClosedChannelException
16:19:15.492	Client session connection error. Starting new connection
16:19:15.539	client Transport send completed: onError, io.rsocket.keepalive.KeepAliveConnection@2e35da9e
16:19:18.552	client Resumable duplex connection reconnected with connection: io.rsocket.internal.ClientServerConnection@52af0cd2
16:19:18.553	Switching transport: client
16:19:18.554	Upstream subscriber requestN: 256
16:19:18.554	Client ResumableConnection reconnected. Sending RESUME frame with state: [impliedPos: 70003, pos: 0]
16:19:18.555	sending ->
Frame => Stream ID: 0 Type: RESUME Flags: 0b0 Length: 44
Data:

16:19:18.576	client Inner connection disconnected: ClosedChannelException
16:19:18.577	Client session connection error. Starting new connection
16:19:18.577	client Transport send completed: onError, io.rsocket.internal.ClientServerConnection@52af0cd2
16:19:21.589	client Resumable duplex connection reconnected with connection: io.rsocket.internal.ClientServerConnection@307a6a6f
16:19:21.590	Switching transport: client
16:19:21.590	Upstream subscriber requestN: 256
16:19:21.590	Client ResumableConnection reconnected. Sending RESUME frame with state: [impliedPos: 70003, pos: 0]
16:19:21.590	sending ->
Frame => Stream ID: 0 Type: RESUME Flags: 0b0 Length: 44
Data:

16:19:41.601	receiving ->
Frame => Stream ID: 0 Type: KEEPALIVE Flags: 0b0 Length: 14
Data:

Issue Analytics

State:
Created 4 years ago
Comments:13 (13 by maintainers)

Top GitHub Comments

1reaction

mostroverkhovcommented, May 21, 2019

Maybe try add .limitRate(n) on receiving side? Then on disconnect there will be at most N items in resume cache.

0reactions

yschimkecommented, May 21, 2019

Changed the cli to use a slower interval timer (1/sec) source and it’s all good. I think the stream from a file source just overwhelms the server when there is no connected client. Not convinced things are in a good state after that point. But it’s working end to end in the happy resume path.

Thanks for the help.

Top Results From Across the Web

When we connected with two call resume all not working #307

I have connected with two calls in a contact. After connected two calls. I have 3 connections in the contact. AgentConnection ActiveInitialConnection ...

Resume of change stream was not possible, as ... - MongoDB

I am running a sharded MongoDB Cluster with a single shard and use change streams to listen to change evens in the database....

How to modify stream on ongoing connection to pause ...

I am seeking some help on how to pause and resume video and audio stream for self and remote user, while on active...

Why Your Resume Isn't Working For You — And How To Fix It

Tailor your resume to the job you are seeking, not to your prior jobs. Review the posted job requirements and make sure that...

Troubleshoot video streaming issues - YouTube TV Help

If you're experiencing issues with video streaming on YouTube TV, try these troubleshooting tips. On a mobile device Restart your device Hold down...