-
Notifications
You must be signed in to change notification settings - Fork 5
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
Wait for publish ack #8
Comments
Here is the documentation of the publisher confirm feature of RabbitMQ. You can also find a nice article here, on how to set this up using the spring-amqp library, which is used by the outboxer. As always implementing this should not be the problem, but finding the right approach how to handle a negative or missing ack is the difficult part here. |
Sorry for commenting on an older issue but has there been any progress towards integrating publisher confirms so far? |
Hey, Unfortunately no. We stopped active development on this repository a while ago... Additionally, we think that there is no good "opinionated" way to provide such a feature as failure handling should always depend on the context and should be motivated by your domain. Feel free to fork and adapt to your context. Above is a linked article that should explain how to do it. |
Hey, thanks for the fast answer and sorry for my late reply! I completely agree with your reasoning. I was just looking for something that I can use for illustration purposes. Turns out a simple polling implementation can be done with a few lines of code and is sufficient for my needs. 🙂 |
Currently, you get an ACK for reaching RabbitMQ, but not for persisting the message.
The text was updated successfully, but these errors were encountered: