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
Today we had a weird case where the exchange we were pushing to stop responding some how... maybe for the 3M message waiting them. (I cannot check the RabbitMQ logs because... they deleted them... don't ask why)
The thing is when we were publishing it seems our flow got stuck there, waiting.
We use context cancel but it seem currently the library doesn't honor the context.
What options do we have?
Implement our own timeout for publishing? I see (maybe wrongly) we can just not waiting for the server confirmation but we prefer to not use that option as this message are kind of important... So we are looking for options to handle "both" situations.
Thanks
The text was updated successfully, but these errors were encountered:
After some further testing I believe my could be if when publishing the channel was closed and the library is trying to reconnect, the publishing wait.
Would it this be a possibility?
Could we have a way to not wait if our message is not that important or if we cannot wait that long?
Basically this is an API call which after some operation send a notification message to a queue, but this API needs to respond as quicker as possible.. 30s delays will kill performance....
Hi,
Today we had a weird case where the exchange we were pushing to stop responding some how... maybe for the 3M message waiting them. (I cannot check the RabbitMQ logs because... they deleted them... don't ask why)
The thing is when we were publishing it seems our flow got stuck there, waiting.
We use context cancel but it seem currently the library doesn't honor the context.
What options do we have?
Implement our own timeout for publishing? I see (maybe wrongly) we can just not waiting for the server confirmation but we prefer to not use that option as this message are kind of important... So we are looking for options to handle "both" situations.
Thanks
The text was updated successfully, but these errors were encountered: