Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/483
Thank you for the complements. The "InterruptedException" essentially means
something want this thread to stop for some reason (here's an overview of
[this](http://www.yegor256.com/2015/10/20/interrupted-exception.html)). At that
point, we just want to proceed without lingering or stopping as best we can.
Also since we are synchronized on the message, when we resume we can be sure
that we are the only ones working on the message at that time. So we just need
to be sure the other thread does it's best to take into account what the state
of the message is.
Also for future reference, you shouldn't rebase other people's commits into
yours. In order to keep track of who did what (and who to blame when things
break, lol) you should just use "git am <patch>".
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
