You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hudson (Commented) (JIRA)" <ji...@apache.org> on 2012/02/07 02:17:00 UTC
[jira] [Commented] (HADOOP-8027) Visiting /jmx on the daemon web
interfaces may print unnecessary error in logs
[ https://issues.apache.org/jira/browse/HADOOP-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201929#comment-13201929 ]
Hudson commented on HADOOP-8027:
--------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #1751 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1751/])
HADOOP-8027. Visiting /jmx on the daemon web interfaces may print unnecessary error in logs. Contributed by Aaron T. Myers.
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1241303
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/jmx/JMXJsonServlet.java
> Visiting /jmx on the daemon web interfaces may print unnecessary error in logs
> ------------------------------------------------------------------------------
>
> Key: HADOOP-8027
> URL: https://issues.apache.org/jira/browse/HADOOP-8027
> Project: Hadoop Common
> Issue Type: Improvement
> Components: metrics
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Harsh J
> Assignee: Aaron T. Myers
> Priority: Minor
> Fix For: 0.24.0, 0.23.1
>
> Attachments: HDFS-2584.patch
>
>
> Logs that follow a {{/jmx}} servlet visit:
> {code}
> 11/11/22 12:09:52 ERROR jmx.JMXJsonServlet: getting attribute UsageThreshold of java.lang:type=MemoryPool,name=Par Eden Space threw an exception
> javax.management.RuntimeMBeanException: java.lang.UnsupportedOperationException: Usage threshold is not supported
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:856)
> ...
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira