[
https://issues.apache.org/jira/browse/CAMEL-14590?focusedWorklogId=389484&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-389484
]
ASF GitHub Bot logged work on CAMEL-14590:
------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Feb/20 16:16
Start Date: 19/Feb/20 16:16
Worklog Time Spent: 10m
Work Description: connormcauliffe-toast commented on pull request #3591:
CAMEL-14590 Camel-Pulsar consumer calls unsubscribe on doStop/doSuspend,
potentially deleting subscription
URL: https://github.com/apache/camel/pull/3591
In the PulsarUtils stopConsumers method all the consumers call
unsubscribe(). This causes the subscription to be deleted if this call comes
from the last consumer. The PR makes the unsubscribe call configurable so that
unwanted subscription deletion can be prevented.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 389484)
Remaining Estimate: 0h
Time Spent: 10m
> 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)
