-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NIFI-6915 Jms Durable non shared subscription is broken #3961
Conversation
} | ||
|
||
@OnScheduled | ||
public void onSchedule(ProcessContext context) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe you have a typo here. I think the logic should be context.getMaxConcurrentTasks() > 1 && isDurableSubscriber(context) && !isShared(context)
. As is, this condition would never be satisfied.
Can you please add a unit test verifying this new behavior? Also, is it possible to add unit test(s) to verify that the issue you're trying to address (changing client IDs for durable non-shared clients on processor restart) is resolved?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right, thank you. I will push the fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed and added unit tests to verify the behavior. You can check without this fix, the unit test will miss a message.
Hi @gardellajuanpablo - this needs to be rebased against master |
1378dfa
to
509c9b3
Compare
Done, I had some troubles to apply rebase. Hope it is ok now. |
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.
17f9a74
to
983fc8b
Compare
travis is green on all builds. local build almost done. reviewed code - looks good. will merge to master shortly - thanks |
…n 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 <joewitt@apache.org>
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.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically
master
)?Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not
squash
or use--force
when pushing to allow for clean monitoring of changes.For code changes:
mvn -Pcontrib-check clean install
at the rootnifi
folder?LICENSE
file, including the mainLICENSE
file undernifi-assembly
?NOTICE
file, including the mainNOTICE
file found undernifi-assembly
?.displayName
in addition to .name (programmatic access) for each of the new properties?For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.