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

JMS - Message acknowledgement #2575

Open
dankristensen opened this issue Apr 11, 2024 · 3 comments
Open

JMS - Message acknowledgement #2575

dankristensen opened this issue Apr 11, 2024 · 3 comments
Labels

Comments

@dankristensen
Copy link
Contributor

We have discussed a bit about acknowledgement, when using CLIENT_ACKNOWLEDGE during the jms connector.

When i try this and my Inbound annotated method throws an Exception, this results in the message being "stuck" in the client.

If the broker restarts for some reason, this will typically mean that the message will be redelivered.

Another approach could be that in the inbound annotated method is surrounded with at try - catch, where the catch will put the unaccepted message on a backout queue.

But this seems like a very general issue, so would it be possible to create an annotation that could take of this?

Like
@Backout(queue="SOME_QUEUE_BACKOUT")

@cescoffier cescoffier added the jms label Apr 12, 2024
@cescoffier cescoffier changed the title Message acknowledgement JMS - Message acknowledgement Apr 12, 2024
@cescoffier
Copy link
Contributor

We cannot add JMS specific annotation. However, we can implement a failure strategy which would do that. We are already doing this for Kafka, and Pulsar.

@dankristensen
Copy link
Contributor Author

That sounds like a brilliant idea. Is it ok, that i do some initial work on this, and that you can follow up on this later on?

I will try to do it like Kafka fault package

@dankristensen
Copy link
Contributor Author

I have been working on this here: #2599 . But need some help to get this completed

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

No branches or pull requests

2 participants