Github user klinvill commented on the issue:
https://github.com/apache/nifi/pull/1290
@jfrazee Apologies for the delayed response. I was running it against NiFi
1.0.0. The client I was working for at the time was using a few non-standard
HL7 messages that were resulting in exceptions. The exceptions weren't really
the problem (the failed messages just require specialized processing). The real
problem was that the exceptions thrown were not HL7Exceptions so the NiFi
processor didn't know where to route the message and the flowfile stayed in the
queue to be processed at a later time. We were handling a large volume of these
messages so the processor quickly got overloaded with the flowfile backlog. We
ended up fixing this locally by simply routing all exceptions to failure so
that the flowfiles would be moved out of the queue. I understand @mattyb149's
point about how catching all exceptions could lead to data loss. Unfortunately
I no longer have access to the messages or workflows that are failing so I'll
go ahead and close this request. Thank you all for the help,
if I run into this situation again I'll add in additional business logic and
submit it back as a pull request.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
