[
https://issues.apache.org/jira/browse/IGNITE-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401880#comment-16401880
]
ASF GitHub Bot commented on IGNITE-7962:
----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/3649
IGNITE-7962 Avoid swallowing unexpected exceptions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7962
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3649.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 #3649
----
commit 2cb6d469e89758684de3391ee679da250173b6b1
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date: 2018-03-16T13:23:03Z
IGNITE-7962 Avoid swallowing unexpected exceptions.
----
> More cases of suppressed exceptions in IsolatedUpdater
> ------------------------------------------------------
>
> Key: IGNITE-7962
> URL: https://issues.apache.org/jira/browse/IGNITE-7962
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.4
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Priority: Major
>
> IsolatedUpdater is a StreamReciever.
> The contract for StreamReciever.recieve() is, @throws
> org.apache.ignite.IgniteException If failed.
> However, there's a number of cases where this doesn't happen and exceptions
> are suppressed after being written in server log. Should replace (or augment)
> log.error()'s with throw new IgniteException().
> See maillist discussion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
