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

Posted to dev@reef.apache.org by "Julia (JIRA)" <ji...@apache.org> on 2016/08/11 18:42:20 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15417730#comment-15417730 ] 

Julia commented on REEF-1523:
-----------------------------

Currently, when the exception happens, we do nothing, looks like this exception doesn't impact the main flow. So I would think we can just do a null checking. If null, log a warning instead of throwing an exception. That at least won't change the current behavior. 

> 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
>
> Currently, when communication between clinet and server is disconnected for whatever reason, mostly after a node in 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)