[ 
https://issues.apache.org/jira/browse/FLUME-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500335#comment-16500335
 ] 

ASF GitHub Bot commented on FLUME-3237:
---------------------------------------

GitHub user turcsanyip opened a pull request:

    https://github.com/apache/flume/pull/210

    FLUME-3237: Handling RuntimeExceptions coming from the JMS provider i…

    …n JMSSource
    
    Handling RuntimeExceptions in the same way as JMSExceptions in order to 
trigger
    the reconnecting mechanism in JMSSource.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/turcsanyip/flume FLUME-3237

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flume/pull/210.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #210
    
----
commit 7585b513140b1ce2a7d2ce58dcd2ffc604fab448
Author: turcsanyi <turcsanyi@...>
Date:   2018-06-04T13:04:27Z

    FLUME-3237: Handling RuntimeExceptions coming from the JMS provider in 
JMSSource
    
    Handling RuntimeExceptions in the same way as JMSExceptions in order to 
trigger
    the reconnecting mechanism in JMSSource.

----


> Handling RuntimeExceptions coming from the JMS provider in JMSSource
> --------------------------------------------------------------------
>
>                 Key: FLUME-3237
>                 URL: https://issues.apache.org/jira/browse/FLUME-3237
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Peter Turcsanyi
>            Assignee: Peter Turcsanyi
>            Priority: Major
>
> JMS providers can return runtime exceptions instead of {{JMSException}} in 
> some cases. Eg. IBM WebSphere MQ throws {{NullPointerException}} in case of a 
> broken connection (more precisely it throws {{JMSException}} first, but 
> subsequent {{receive, commit, rollback,}} etc. calls lead to NPE).
> These exceptions should be handled the same way as {{JMSException}} (because 
> they are coming from the JMS provider) and should trigger the same reconnect 
> mechanism in {{JMSSource}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@flume.apache.org
For additional commands, e-mail: issues-h...@flume.apache.org

Reply via email to