[
https://issues.apache.org/jira/browse/IGNITE-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192816#comment-16192816
]
ASF GitHub Bot commented on IGNITE-6545:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/2807
IGNITE-6545: Failure during Ignite Service.cancel() can break normal
shutdown process.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6545
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2807.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 #2807
----
commit eb0a73be56d450c12ed75090b726b5e89b586cae
Author: Andrey V. Mashenkov <[email protected]>
Date: 2017-10-05T12:18:21Z
IGNITE-6545: Failure during Ignite Service.cancel() can break normal
shutdown process.
----
> Failure during Ignite Service.cancel() can break normal shutdown process.
> -------------------------------------------------------------------------
>
> Key: IGNITE-6545
> URL: https://issues.apache.org/jira/browse/IGNITE-6545
> Project: Ignite
> Issue Type: Bug
> Components: managed services
> Environment:
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Labels: newbie
> Fix For: 2.4
>
>
> org.apache.ignite.services.Service is a public interface, but Ignite fully
> relies it's cacel method is implemented properly and throws no errors.
> However, if one of services fails on cancel(), then other services may not be
> stopped properly as well as their executor pools.
> We should wrap Service.cancel method in try-catch to avoid this.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
