accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-3958) Monitor.fetchData should check for null instance name
Date Mon, 24 Aug 2015 17:03:46 GMT

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

Josh Elser resolved ACCUMULO-3958.
----------------------------------
    Resolution: Fixed

> Monitor.fetchData should check for null instance name
> -----------------------------------------------------
>
>                 Key: ACCUMULO-3958
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3958
>             Project: Accumulo
>          Issue Type: Bug
>          Components: monitor
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.6.4, 1.7.1, 1.8.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Had an odd situation where the monitor would throw an NPE constantly when I tried to
view any page.
> It was throwing a NPE trying to accessed the cached instance name. It appears that {{HdfsZooInstance.getInstance().getInstanceName(}}
may return null, but the monitor code is not written to account for that.
> The monitor should check for null values before setting the instance name into {{cachedInstanceName}}.
When the instance name is null, it should reschedule the timertask to try to fetch a (non-null)
instance name.



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

Mime
View raw message