You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/09/05 09:16:20 UTC

[jira] [Commented] (FLINK-4451) Throw exception when remote connection cannot be resolved

    [ https://issues.apache.org/jira/browse/FLINK-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464545#comment-15464545 ] 

Till Rohrmann commented on FLINK-4451:
--------------------------------------

Fixed via 0cf2a822b6872ee4f3f0c99f0fcee71affaeaee5

> Throw exception when remote connection cannot be resolved
> ---------------------------------------------------------
>
>                 Key: FLINK-4451
>                 URL: https://issues.apache.org/jira/browse/FLINK-4451
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Distributed Coordination
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>
> The {{RpcService}} implementation should throw an exception (returned in the future) if {{RpcService.connect(address, type)}} cannot connect to the remote {{RpcEndpoint}}.
> At the moment the {{AkkaRpcService}} does not check that the {{IdentifyActor}} message contains a valid {{ActorRef}} and throws due to that a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)