You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Kurbanov (JIRA)" <ji...@apache.org> on 2018/04/16 14:16:00 UTC
[jira] [Commented] (IGNITE-8154) Add an ability to provide
ExceptionListener to JmsStreamer
[ https://issues.apache.org/jira/browse/IGNITE-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439494#comment-16439494 ]
Anton Kurbanov commented on IGNITE-8154:
----------------------------------------
Artifact links: [PR|https://github.com/apache/ignite/pull/3828] / [TC|https://ci.ignite.apache.org/viewQueued.html?itemId=1212512&tab=queuedBuildOverviewTab]
[~slukyanov], [~vkulichenko], could you please review?
> Add an ability to provide ExceptionListener to JmsStreamer
> ----------------------------------------------------------
>
> Key: IGNITE-8154
> URL: https://issues.apache.org/jira/browse/IGNITE-8154
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
> Affects Versions: 2.4
> Reporter: Valentin Kulichenko
> Assignee: Anton Kurbanov
> Priority: Major
> Fix For: 2.5
>
>
> JMS API allows to provide custom {{ExceptionListener}} that is invoked when an exception occurs within JMS queue/topic. Currently, {{JmsStreamer}} doesn't use this in any way which creates two issues:
> * If there is an exception, it's lost and not even logged.
> * User can't provide their own listener.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)