[
https://issues.apache.org/jira/browse/CAMEL-14590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040238#comment-17040238
]
Masa commented on CAMEL-14590:
------------------------------
I believe we should remove the unsubscribe call entirely and not make it
configurable.
We do not want to destroy subscriptions when the application is shutdown or a
route is restarted.
"Unsubscribe" should be Pulsar admin functionality and not part of a Camel
component.
> Camel-Pulsar consumer calls unsubscribe on doStop/doSuspend, potentially
> deleting subscription
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-14590
> URL: https://issues.apache.org/jira/browse/CAMEL-14590
> Project: Camel
> Issue Type: Improvement
> Components: camel-pulsar
> Reporter: Connor McAuliffe
> Priority: Major
> Fix For: 3.2.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the PulsarUtils [stopConsumers
> method|https://github.com/apache/camel/blob/master/components/camel-pulsar/src/main/java/org/apache/camel/component/pulsar/utils/PulsarUtils.java]
> all the consumers call unsubscribe(). This causes the subscription to be
> deleted if this call comes from the last consumer. I do not know if this is
> intentional behavior but it seems to be dangerous (and has caused some issues
> for us without realizing it). If this is intentional, can we make it
> configurable to avoid doing this? Or if it is not intentional can we just
> remove the call entirely?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
