Skip to content

NIFI-7039 - Fix: PublishJMS can fail with ConcurrentModificationException#3995

Closed
tpalfy wants to merge 1 commit intoapache:masterfrom
tpalfy:NIFI-7039
Closed

NIFI-7039 - Fix: PublishJMS can fail with ConcurrentModificationException#3995
tpalfy wants to merge 1 commit intoapache:masterfrom
tpalfy:NIFI-7039

Conversation

@tpalfy
Copy link
Contributor

@tpalfy tpalfy commented Jan 17, 2020

https://issues.apache.org/jira/browse/NIFI-7039

PublishJMS outgoing flowfile attribute cleanup could lead to ConcurrentModificationException

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:

  • Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
  • Have you written or updated unit tests to verify your changes?
  • Have you verified that the full build is successful on both JDK 8 and JDK 11?
  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
  • If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
  • If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

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.

@asfgit asfgit closed this in b35ad7c Jan 19, 2020
natural pushed a commit to natural/nifi that referenced this pull request Feb 1, 2020
…e attribute cleanup could lead to ConcurrentModificationException

Signed-off-by: Joe Witt <joewitt@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant