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 we debug, we also see the message: "unknown resume token".
Steps to Reproduce
exportconstcreateConnector=(url: string,clientUuid: string)=>{constconnector=newRSocketConnector({setup: {// ms btw sending keepalive to serverkeepAlive: 60000,// ms timeout if no keepalive responselifetime: 180000,payload: {data: Buffer.from(clientUuid),metadata: Buffer.from(String.fromCharCode(clientUuid.length)+clientUuid)},// format of `data`dataMimeType: 'application/json',// format of `metadata`metadataMimeType: 'message/x.rsocket.routing.v0',},transport: newWebsocketClientTransport({url: url}),resume: {tokenGenerator: ()=>Buffer.from(clientUuid),reconnectFunction: (attemptCount)=>newPromise((resolve,reject)=>{if(attemptCount>9)reject();console.log("reconnect attempt: "+attemptCount);setTimeout(resolve,9*1000);})}});returnconnector;};
For JAVA, just use the default configuration for spring-boot-starter-rsocket with this yml:
Expected Behavior
We use react-js on client side with this resume code:
We use spring-boot-starter-rsocket on the server side.
We expect it resumes after the shutdown and restart the Spring server.
Actual Behavior
We get this error on the client side:
When we debug, we also see the message: "unknown resume token".
Steps to Reproduce
For JAVA, just use the default configuration for spring-boot-starter-rsocket with this yml:
Possible Solution
The root cause for this error might be that the server validates token using in-memory store, Implementing a permanent store for tokens might help.
Your Environment
package.json
gradle:
implementation 'org.springframework.boot:spring-boot-starter-rsocket'
The text was updated successfully, but these errors were encountered: