[
https://issues.apache.org/jira/browse/AMBARI-16187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278747#comment-15278747
]
Hudson commented on AMBARI-16187:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.2 #691 (See
[https://builds.apache.org/job/Ambari-branch-2.2/691/])
AMBARI-16187. Jersey and Jetty logs should go to server log file.
(mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ce2e59f220f6469d7f2d381e14b75b1c44e47344])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* ambari-server/conf/unix/log4j.properties
* ambari-server/pom.xml
> Jersey and Jetty logs should go to server log file
> --------------------------------------------------
>
> Key: AMBARI-16187
> URL: https://issues.apache.org/jira/browse/AMBARI-16187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Myroslav Papirkovskyi
> Assignee: Myroslav Papirkovskyi
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16187.patch
>
>
> Jersey and Jetty use JUL as logging framework which is not configured, so
> logs are printed to out file. We should intercept log entries and print them
> to server log.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
