flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4451) Throw exception when remote connection cannot be resolved
Date Wed, 24 Aug 2016 11:28:20 GMT

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

ASF GitHub Bot commented on FLINK-4451:

Github user tillrohrmann commented on the issue:

    Akka will return an empty `ActorIdentity` message if no actor could be found for the `Identify`
message. I assume that this is the case if Akka cannot reach the remote actor system or if
the remote actor system tells that there is no such actor with the given Akka URL.

> 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

View raw message