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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/09/04 09:17:51 UTC

[jira] [Commented] (HADOOP-11048) user/custom LogManager fails to load if the client classloader is enabled

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

Hadoop QA commented on HADOOP-11048:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12666423/HADOOP-11048.patch
  against trunk revision 8f1a668.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-common-project/hadoop-common.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/4646//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/4646//console

This message is automatically generated.

> user/custom LogManager fails to load if the client classloader is enabled
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-11048
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11048
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 2.6.0
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>            Priority: Minor
>         Attachments: HADOOP-11048.patch
>
>
> If the client classloader is enabled (HADOOP-10893) and you happen to use a user-provided log manager via -Djava.util.logging.manager, it fails to load the custom log manager:
> {noformat}
> Could not load Logmanager "org.foo.LogManager"
> java.lang.ClassNotFoundException: org.foo.LogManager
>     at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
>     at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>     at java.util.logging.LogManager$1.run(LogManager.java:191)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at java.util.logging.LogManager.<clinit>(LogManager.java:181)
>     at java.util.logging.Logger.demandLogger(Logger.java:339)
>     at java.util.logging.Logger.getLogger(Logger.java:393)
>     at com.google.common.collect.MapMakerInternalMap.<clinit>(MapMakerInternalMap.java:136)
>     at com.google.common.collect.MapMaker.makeCustomMap(MapMaker.java:602)
>     at com.google.common.collect.Interners$CustomInterner.<init>(Interners.java:59)
>     at com.google.common.collect.Interners.newWeakInterner(Interners.java:103)
>     at org.apache.hadoop.util.StringInterner.<clinit>(StringInterner.java:49)
>     at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2293)
>     at org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2185)
>     at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2102)
>     at org.apache.hadoop.conf.Configuration.get(Configuration.java:851)
>     at org.apache.hadoop.util.RunJar.run(RunJar.java:179)
>     at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> {noformat}
> This is caused because Configuration.loadResources() is invoked before the client classloader is created and made available.



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