[
https://issues.apache.org/jira/browse/CAMEL-17671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494468#comment-17494468
]
Tom Cassimon commented on CAMEL-17671:
--------------------------------------
It looks like the component could support transactionality, while debugging the
code and looking for the best solution I noticed if i kill my test jvm the
message stays on the queue in azure. I took a brief look at the azure component
code but didn't directly found a pointer of where the transactionality could or
should be implemented.
> camel-azure - Add transaction support to Azure ServiceBus
> ---------------------------------------------------------
>
> Key: CAMEL-17671
> URL: https://issues.apache.org/jira/browse/CAMEL-17671
> Project: Camel
> Issue Type: New Feature
> Components: camel-azure
> Reporter: Tom Cassimon
> Priority: Major
>
> I would like to see the feature of transactions in the azure servicebus when
> using queues.
> The use case I would like to have is that when a message is processed in a
> route with an azure servicebus consumer and an error occurs during
> processing, that the message is not aknowledged to the azure servicebus
> broker, resulting in the message to re-appear on the queue and can be
> processed by the same or another listener instance on the queue.
> If i scroll to the configuration in Azure of the service bus I see a max
> delivery count setting, so i presume the feature is possible in the service
> bus component but not used in the camel service bus component.
> An simple example of a route that should not aknowledge the message on the
> ServiceBus component, and should lead to the message to re-appear on the
> queue for a redelivery attempt.
> {code:java}
> from("azure-servicebus://<redacted>")
> .autoStartup(true)
> .transacted()
> .throwException(new RuntimeException())
> .end(); {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
