Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 20 Apr 2011 23:33:21 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <802073789.71751.1303342401222.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <24790298.36271291756752604.JavaMail.jira@thor>
Subject: [jira] [Commented] (HDFS-1531) Clean up stack traces due to
 duplicate MXBean registration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HDFS-1531:
------------------------------

Integrated in Hadoop-Hdfs-trunk #643 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk/643/])
    

> Clean up stack traces due to duplicate MXBean registration
> ----------------------------------------------------------
>
>                 Key: HDFS-1531
>                 URL: https://issues.apache.org/jira/browse/HDFS-1531
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, name-node
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Trivial
>             Fix For: 0.22.0
>
>         Attachments: hdfs-1531.txt
>
>
> In the minicluster unit tests, we try to register MXBeans for each DN, but since the JMX context is JVM-wide, we get a InstanceAlreadyExistsException for all but the first. This stack trace clutters test logs a lot.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira