501 (FRAME-ERROR) - after indeterminate amount of large messages

[GlennButera]

501 (FRAME-ERROR) - after indeterminate amount of large messages

[cressie176]

Hi @GlennButera,

I haven't come across this before, but other RabbitMQ issues I've found online suggest this problem can occur when publishing from different threads using the same channel. If I understand correctly, a message published by one thread is being mutated by another thread before it is sent, invalidating it.

While Node.js isn't multithreaded, you can get this behaviour when sharing data between asynchronous code. You're using JSON.stringify to serializse _packet so I believe that must be safe, however you are passing in _options, so potentially that is being mutated. Can you try deep cloning _options immediately so that neither it, or the headers sub-document have any chance to be mutated?

[cressie176]

You could also try not sharing the channel. This will be a little slower though.

[GlennButera]

@cressie176 I have tried "deep cloning" the _options immediately wherever it was being used by doing a JSON.parse(JSON.stringify(_options));. The issue still occurred.

[cressie176]

Hi @GlennButera,

I've created what I hoped would be a minimal reproducible example based on your description of the problem, but it works fine. Are you able to fork this, test it in your environment, and make the necessary amends to reproduce the frame error please?

FYI, the example uses confirm channels, but I also tried with regular ones.

[cressie176]

Any update @GlennButera?

[GlennButera]

@cressie176 My apologies, we were not able to reproduce with the minimal reproducible example. We have decided to move on from the issue and are going about a different solution that will remove this issue from our code by not leveraging RabbitMQ in the same way.