[
https://issues.apache.org/jira/browse/NIFI-6915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018942#comment-17018942
]
ASF subversion and git services commented on NIFI-6915:
-------------------------------------------------------
Commit c1301e196c5be89819e702ec76912f3c426f3055 in nifi's branch
refs/heads/master from Gardella Juan Pablo
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c1301e1 ]
NIFI-6915 This closes #3961. Jms Durable non shared subscription is broken
Revert NIFI-4834 enhancement for durable non shared consumers only.
Updated also AbstractJMSProcessor class to be public. The testing are not
working
without that change, as org.apache.nifi.jms.processors.PublishJMSIT and
org.apache.nifi.jms.processors.ConsumeJMSIT are not working, as @OnSchedule
method is not called (because it is not public).
The method org.apache.nifi.util.StandardProcessorTestRunner.run(int iterations,
boolean stopOnFinish, boolean initialize, long runWait) uses
ReflectionUtils.invokeMethodsWithAnnotation which does not call non public
methods.
Signed-off-by: Joe Witt <[email protected]>
> 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 20m
> 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)
