You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/11/02 10:51:00 UTC
[jira] [Commented] (FLINK-10655) RemoteRpcInvocation not
overwriting ObjectInputStream's ClassNotFoundException
[ https://issues.apache.org/jira/browse/FLINK-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672921#comment-16672921 ]
ASF GitHub Bot commented on FLINK-10655:
----------------------------------------
tillrohrmann commented on issue #6920: [FLINK-10655][rpc] fix RemoteRpcInvocation not overwriting ObjectInputStream's ClassNotFoundException
URL: https://github.com/apache/flink/pull/6920#issuecomment-435341118
This PR is based against `release-1.6`. Please mark this PR as a backport and open a new one against the `master` branch. Thanks!
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> RemoteRpcInvocation not overwriting ObjectInputStream's ClassNotFoundException
> ------------------------------------------------------------------------------
>
> Key: FLINK-10655
> URL: https://issues.apache.org/jira/browse/FLINK-10655
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.5.4, 1.6.1, 1.7.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.6, 1.6.3, 1.7.0
>
>
> {{RemoteRpcInvocation}} tries to give a more detailed {{ClassNotFoundException}} if the method type/argument deserialization fails. However, it turns out, once {{ObjectInputStream}} has received a {{ClassNotFoundException}}, it will not overwrite this anymore and we can therefore not provide a more detailed {{ClassNotFoundException}}.
> Instead, the least invasive solution would be to add a suppressed {{ClassNotFoundException}} to the existing one. While at it, we could also add more details, i.e. the successfully deserialized types and arguments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)