Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publishing Timeout #189

Open
dgonzalezKentech opened this issue Oct 1, 2024 · 1 comment
Open

Publishing Timeout #189

dgonzalezKentech opened this issue Oct 1, 2024 · 1 comment

Comments

@dgonzalezKentech
Copy link

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

@dgonzalezKentech
Copy link
Author

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....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant