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
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?
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.
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")
The text was updated successfully, but these errors were encountered: