[
https://issues.apache.org/jira/browse/FLUME-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539974#comment-16539974
]
ASF subversion and git services commented on FLUME-3237:
--------------------------------------------------------
Commit a76e2e9f2cde18f3b7548b991535a3151425de12 in flume's branch
refs/heads/trunk from [~fszabo]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=a76e2e9 ]
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.
This closes #210
Reviewers: Endre Major, Ferenc Szabo
(Peter Turcsanyi via Ferenc Szabo)
> 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: [email protected]
For additional commands, e-mail: [email protected]
