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

Posted to dev@reef.apache.org by "Mariia Mykhailova (JIRA)" <ji...@apache.org> on 2016/08/12 23:03:20 UTC

[jira] [Resolved] (REEF-1523) Fix Null Point exception in NameServer when message is null

     [ https://issues.apache.org/jira/browse/REEF-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mariia Mykhailova resolved REEF-1523.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.16

Resolved via [PR 1093|https://github.com/apache/reef/pull/1093]

> Fix Null Point exception in NameServer when message is null
> -----------------------------------------------------------
>
>                 Key: REEF-1523
>                 URL: https://issues.apache.org/jira/browse/REEF-1523
>             Project: REEF
>          Issue Type: Improvement
>            Reporter: Julia
>            Assignee: Julia
>             Fix For: 0.16
>
>
> Currently, when communication between clinet and server is disconnected for whatever reason, mostly after a node is unregistered, the message received in NameServer is null. When we use message.Link, it causes null point exception, polluted the the driver log. We should handle this case instead of letting null point exception to throw. 



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