[jira] [Updated] (NIFI-6915) Jms Durable non shared subscription is broken

2020-01-19 Thread Joe Witt (Jira)


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

Joe Witt updated NIFI-6915:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Jms Durable non shared 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
>Assignee: Gardella Juan Pablo
>Priority: Critical
> Fix For: 1.11.0
>
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> The enhancement NIFI-4834 broke JMS non shared Durable subscriptions. It may 
> lose messages after stopping and starting a {{ConsumeJMS}} processor as 
> [client ID is always 
> different|https://github.com/apache/nifi/pull/2445/commits/cd091103e4a76e7b54e00257e5e18eaab3d389ec#diff-4ce7e53c92829e48b85959da41653f2bR189]
>  since NIFI-4834.
> Using different client identifiers, makes the consumer missing messages after 
> it is restarted. The problem is when some messages were published to the 
> topic during the consumer is not running.
> 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)


[jira] [Updated] (NIFI-6915) Jms Durable non shared subscription is broken

2020-01-19 Thread Joe Witt (Jira)


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

Joe Witt updated NIFI-6915:
---
Fix Version/s: 1.11.0

> Jms Durable non shared 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
>Assignee: Gardella Juan Pablo
>Priority: Critical
> Fix For: 1.11.0
>
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> The enhancement NIFI-4834 broke JMS non shared Durable subscriptions. It may 
> lose messages after stopping and starting a {{ConsumeJMS}} processor as 
> [client ID is always 
> different|https://github.com/apache/nifi/pull/2445/commits/cd091103e4a76e7b54e00257e5e18eaab3d389ec#diff-4ce7e53c92829e48b85959da41653f2bR189]
>  since NIFI-4834.
> Using different client identifiers, makes the consumer missing messages after 
> it is restarted. The problem is when some messages were published to the 
> topic during the consumer is not running.
> 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)


[jira] [Updated] (NIFI-6915) Jms Durable non shared subscription is broken

2020-01-06 Thread Gardella Juan Pablo (Jira)


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

Gardella Juan Pablo updated NIFI-6915:
--
Status: Patch Available  (was: In Progress)

> Jms Durable non shared 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.9.2, 1.9.1, 1.10.0, 1.9.0, 1.8.0, 1.7.0, 1.6.0
> Environment: All
>Reporter: Gardella Juan Pablo
>Assignee: Gardella Juan Pablo
>Priority: Critical
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The enhancement NIFI-4834 broke JMS non shared Durable subscriptions. It may 
> lose messages after stopping and starting a {{ConsumeJMS}} processor as 
> [client ID is always 
> different|https://github.com/apache/nifi/pull/2445/commits/cd091103e4a76e7b54e00257e5e18eaab3d389ec#diff-4ce7e53c92829e48b85959da41653f2bR189]
>  since NIFI-4834.
> Using different client identifiers, makes the consumer missing messages after 
> it is restarted. The problem is when some messages were published to the 
> topic during the consumer is not running.
> 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)


[jira] [Updated] (NIFI-6915) Jms Durable non shared subscription is broken

2020-01-06 Thread Gardella Juan Pablo (Jira)


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

Gardella Juan Pablo updated NIFI-6915:
--
Summary: Jms Durable non shared subscription is broken  (was: Jms Durable 
subscription is broken)

> Jms Durable non shared 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
>Assignee: Gardella Juan Pablo
>Priority: Critical
>
> The enhancement NIFI-4834 broke JMS non shared Durable subscriptions. It may 
> lose messages after stopping and starting a {{ConsumeJMS}} processor as 
> [client ID is always 
> different|https://github.com/apache/nifi/pull/2445/commits/cd091103e4a76e7b54e00257e5e18eaab3d389ec#diff-4ce7e53c92829e48b85959da41653f2bR189]
>  since NIFI-4834.
> Using different client identifiers, makes the consumer missing messages after 
> it is restarted. The problem is when some messages were published to the 
> topic during the consumer is not running.
> 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)