You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flume.apache.org by "Peter Turcsanyi (JIRA)" <ji...@apache.org> on 2018/07/11 14:45:01 UTC
[jira] [Updated] (FLUME-3237) Handling RuntimeExceptions coming
from the JMS provider in JMSSource
[ https://issues.apache.org/jira/browse/FLUME-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Turcsanyi updated FLUME-3237:
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
1.8.1
Status: Resolved (was: Patch Available)
> 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
> Fix For: 1.8.1, 1.9.0
>
>
> 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-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org