hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-11572) Datanucleus loads Log4j1.x Logger from AppClassLoader
Date Thu, 27 Aug 2015 06:34:46 GMT

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

Prasanth Jayachandran commented on HIVE-11572:
----------------------------------------------

[~gopalv] The order of loading is HIVE_CONF_DIR, HIVE_LIBS, HADOOP_CLASSPATH and finally HIVE_CLASSPATH.
This is the order the attached patch maintains. Does this order looks good to you? If so I
will go ahead and commit the patch. 

> Datanucleus loads Log4j1.x Logger from AppClassLoader
> -----------------------------------------------------
>
>                 Key: HIVE-11572
>                 URL: https://issues.apache.org/jira/browse/HIVE-11572
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Logging
>    Affects Versions: 2.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>             Fix For: 2.0.0
>
>         Attachments: HIVE-11572.patch
>
>
> As part of HIVE-11304, we moved from Log4j1.x to Log4j2. But DataNucleus log messages
gets logged to console when launching the hive cli. The reason is DataNucleus is trying to
load Log4j1.x Logger by traversing its class loader. Although we use log4j-1.2-api bridge
we are loading log4j-1.2.16 jar that was pulled by ZooKeeper. We should make sure that there
is no log4j-1.2.16 in datanucleus classloader hierarchy (classpath). 
> DataNucleus logger has this 
> {code}
> NucleusLogger.class.getClassLoader().loadClass("org.apache.log4j.Logger");
>             loggerClass = org.datanucleus.util.Log4JLogger.class;
> {code}



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

Mime
View raw message