[
https://issues.apache.org/jira/browse/AMBARI-25176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786810#comment-16786810
]
Hudson commented on AMBARI-25176:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.7 #440 (See
[https://builds.apache.org/job/Ambari-branch-2.7/440/])
AMBARI-25176 Misconfiguration of jersey log in log4j.properties (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=2abc05ccd76dc995923f7c0b1c3ea74fc7ba7f88])
* (edit) ambari-server/conf/unix/log4j.properties
> 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)
