[
https://issues.apache.org/jira/browse/IGNITE-8501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476070#comment-16476070
]
ASF GitHub Bot commented on IGNITE-8501:
----------------------------------------
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4004
IGNITE-8501: Retry on GridServiceNotFoundException in GridServiceProxy
needs to be fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8501
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4004.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 #4004
----
commit 0e4c59cd8fa6432df5c8092d0ff2640f6ff1e7d4
Author: Stanislav Lukyanov <stanlukyanov@...>
Date: 2018-05-15T15:24:06Z
IGNITE-8501: Fixed retry on exception in GridServiceProxy::invokeMethod.
commit da07b484ede0186ddc757e3712a033e7d99c77c0
Author: Stanislav Lukyanov <stanlukyanov@...>
Date: 2018-05-15T16:06:37Z
IGNITE-8501: Added test case with a service with long initialization.
----
> Retry on GridServiceNotFoundException in GridServiceProxy needs to be fixed
> ---------------------------------------------------------------------------
>
> Key: IGNITE-8501
> URL: https://issues.apache.org/jira/browse/IGNITE-8501
> Project: Ignite
> Issue Type: Bug
> Reporter: Stanislav Lukyanov
> Assignee: Stanislav Lukyanov
> Priority: Major
> Fix For: 2.6
>
>
> `GridServiceProxy::invokeMethod` attempts to invoke a method of an Ignite
> service and performs retries in case the invocation procedure throws
> `GridServiceNotFoundException` or `ClusterTopologyCheckedException` (these
> exceptions may be thrown in case the service assignments were already
> calculated, but the service instance was not yet created and initialized on
> the affinity server).
> After the fix IGNITE-7904 the exception type thrown by the remote invocation
> code changed to `IgniteCheckedException` (with a cause being
> `GridServiceNotFoundException` or `ClusterTopologyCheckedException`). Because
> of that, the retry doesn't work now.
> Need to fix the code to correctly handle new exception chain.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
