INVALID_RPC_CORRELATION_ID

Question

INVALID_RPC_CORRELATION_ID

caracal7 opened this issue 3 years ago · comments

mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3haxus-2k18hpbb4ta
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3haxur-1y3hg5m5kpr
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3has8e-2ak5ckl6a43
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3hb0t1-13btaeeysu7i
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3hb1ya-17mldyimtrq
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3hb203-3zulfk4mfi9
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3hb3ga-4dmpfdm1q4p
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3haw23-1knv574lnnw
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3haw40-2gxgvvc5li8
mp       | STDERR: broker.js INVALID_RPC_CORRELATION_ID | name: smile with correlation id: km3haxur-11opb0iffgd

What does it mean?
"smile" it is a name of RPC method.

Problem solved after restart server. I don't know how to reproduce error

jaime echegaray zipper · Answer 1 · Mon Mar 15 2021 07:45:33 GMT+0800 (China Standard Time)

Hi, which client and server version are you usign?

Yasser Fadl · Answer 2 · Mon Mar 15 2021 20:53:19 GMT+0800 (China Standard Time)

INVALID_RPC_CORRELATION_ID means the RPC was responded to twice, or that it timed out and then recieved a response.

What is your RPC timeout values?

Dmitrii Vasilev · Answer 3 · Mon Mar 15 2021 21:01:56 GMT+0800 (China Standard Time)

What is your RPC timeout values?

rpc:
  # Timeout for client RPC acknowledgement
  ackTimeout: 1000
  # Timeout for actual RPC provider response
  responseTimeout: 10000

I found what this error appears then I don't have connection to remote MySQL from RPC

Dmitrii Vasilev · Answer 4 · Mon Mar 15 2021 21:04:22 GMT+0800 (China Standard Time)

Hi, which client and server version are you usign?

latest versions from npm

jaime echegaray zipper · Answer 5 · Tue Mar 16 2021 08:55:36 GMT+0800 (China Standard Time)

I found what this error appears then I don't have connection to remote MySQL from RPC

Yes that happens usually if the async action takes longer than the reponseTimeout, it will send the timeout message and then when the async action is completed will try to send the response and thus you'll get that error. If you have long running actions or slow connections increase the responseTimeout or respond to the rpc with some id (record/url/etc) that can be queried later for the final result.

Yasser Fadl · Answer 6 · Tue Mar 16 2021 18:00:50 GMT+0800 (China Standard Time)

yup! think of it sort of like a lambda expiry event, except we can't force the client to stop running code since we don't own the process

jaime echegaray zipper · Answer 7 · Fri Mar 19 2021 00:43:51 GMT+0800 (China Standard Time)

Hi, I'm going to close this and open an issue on the website repo in order to document it.
Please reopen if there are other related problems.