ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-16187) Jersey and Jetty logs should go to server log file
Date Fri, 29 Apr 2016 19:10:12 GMT

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

Hadoop QA commented on AMBARI-16187:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12801482/AMBARI-16187.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6734//console

This message is automatically generated.

> 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)

Mime
View raw message