Replies: 3 comments
-
|
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
|
We don't have enough information to suggest anything specific. There are no details on what "the error" is. You can inspect how many messages are scheduled for delivery in a given exchange. The exchange does not replicate any of the data it stores. Both the number of "scheduled" messages and exchange publishing rates will help narrow things down. This plugin has very important limitations |
Beta Was this translation helpful? Give feedback.
-
|
I tried to create a diagram which shows what and how we are working on this
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a scenario as follow. I have an exchange
Ewhich is bind with queueQ, have a scheduler which puts around 1000 messages on the exchange and all the messages are passed to the queue and I receive them on the listener, while I am processing the messages if a error happens messages are send to a other fanout delayed exchangeFDwith a delay of 60s and this process is repeated until all the messages are processed. The issue is for some reason some messages which are being put onFDare getting lost with error warningBeta Was this translation helpful? Give feedback.
All reactions