[
https://issues.apache.org/jira/browse/IGNITE-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305251#comment-16305251
]
ASF GitHub Bot commented on IGNITE-7239:
----------------------------------------
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/3310
IGNITE-7239 - In case of not serializable cache update response, futu…
…re on node requester will never complete
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7239
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3310.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 #3310
----
commit e0a1ec657b6e638d4ed28fc3d4db4ff552929cff
Author: dkarachentsev <dkarachentsev@...>
Date: 2017-12-28T09:32:06Z
IGNITE-7239 - In case of not serializable cache update response, future on
node requester will never complete
----
> In case of not serializable cache update response, future on node requester
> will never complete
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-7239
> URL: https://issues.apache.org/jira/browse/IGNITE-7239
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.3
> Reporter: Dmitry Karachentsev
> Assignee: Dmitry Karachentsev
> Priority: Minor
>
> To avoid such hang, if response could not be serialized, create other
> response with text of the error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
