You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2019/03/13 16:59:00 UTC

[jira] [Resolved] (AMBARI-25176) Misconfiguration of jersey log in log4j.properties

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

Robert Levas resolved AMBARI-25176.
-----------------------------------
    Resolution: Fixed

> Misconfiguration of jersey log in log4j.properties
> --------------------------------------------------
>
>                 Key: AMBARI-25176
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25176
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Chen Zhi
>            Priority: Major
>              Labels: CI, pull-request-available
>             Fix For: trunk, 2.7.4
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> In the [AMBARI-16187|https://issues.apache.org/jira/browse/AMBARI-16187], we have intercepted log entries and redirected jersey log to server log. To avoid too many logs from jersey, we also changed the default log level (default -> WARN) for jersey library. However, the jersey we used in ambari-server is the older version from Sun, not from the Glassfish, so the correct logger name should be "com.sun.jersey".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)