[
https://issues.apache.org/jira/browse/FLUME-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539975#comment-16539975
]
ASF GitHub Bot commented on FLUME-3237:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/flume/pull/210
> 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
