[ 
https://issues.apache.org/jira/browse/NIFI-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gardella Juan Pablo updated NIFI-6915:
--------------------------------------
    Description: 
The enhancement NIFI-4834 broke JMS Durable subscriptions because after stop 
and start a {{ConsumeJMS}} processor the [client ID is always 
different|https://github.com/apache/nifi/pull/2445/commits/cd091103e4a76e7b54e00257e5e18eaab3d389ec#diff-4ce7e53c92829e48b85959da41653f2bR189].
 

A simple solution is to keep old behavior if it is a durable subscriber. 

 

 

 

  was:
The enhancement NIFI-4834 broke JMS Durable subscriptions because after stop 
and start a {{ConsumeJMS}} processor the [client ID is always 
different|https://github.com/apache/nifi/pull/2445/commits/cd091103e4a76e7b54e00257e5e18eaab3d389ec#diff-4ce7e53c92829e48b85959da41653f2bR189].
 

A simple solution is to keep old behavior if it is a durable subscriber. 
Ideally, for durable subscribers and to keep the scalabilty introduced at 
NIFI-4834, a possible solution may be is to hold in zookeeper the previous 
assigned client id values.

 

 

 


> Jms Durable subscription is broken
> ----------------------------------
>
>                 Key: NIFI-6915
>                 URL: https://issues.apache.org/jira/browse/NIFI-6915
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0, 1.9.1, 1.9.2
>         Environment: All
>            Reporter: Gardella Juan Pablo
>            Priority: Critical
>
> The enhancement NIFI-4834 broke JMS Durable subscriptions because after stop 
> and start a {{ConsumeJMS}} processor the [client ID is always 
> different|https://github.com/apache/nifi/pull/2445/commits/cd091103e4a76e7b54e00257e5e18eaab3d389ec#diff-4ce7e53c92829e48b85959da41653f2bR189].
>  
> A simple solution is to keep old behavior if it is a durable subscriber. 
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to