[
https://issues.apache.org/jira/browse/NIFI-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845392#comment-16845392
]
Koji Kawamura commented on NIFI-6022:
-------------------------------------
Hi [~slyouts]. Thanks for reporting this, and providing the PR. I've added
'contributor' role to your JIRA account so that you can assign yourself to NiFi
JIRAs. (I've assigned you this time)
BTW, the intent of this fix is to throwing the original exception instead of
the one thrown when we call 'session.recover()'. Is that correct? If so, more
descriptive JIRA title would be appreciated. For example, "ConsumeJMS should
throw the original exception when session.recover fails". I'll post few review
comments on the PR as well. Thanks!
> ConsumeJMS - admin yielding
> ---------------------------
>
> Key: NIFI-6022
> URL: https://issues.apache.org/jira/browse/NIFI-6022
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.7.1
> Reporter: Steven Youtsey
> Assignee: Steven Youtsey
> Priority: Major
> Labels: easyfix
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Processor admin yields when session with JMS provider is closed.
> When an exception occurs (no idea what as it was stepped on) and the session
> is closed, the exception handler attempts to use the session and another
> exception is thrown and not caught by the processor. See JMSConsumer, line
> 129. Need to wrap that with a try/catch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
