From issues-return-72614-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Aug 21 15:57:03 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 65E8E180677 for ; Tue, 21 Aug 2018 15:57:03 +0200 (CEST) Received: (qmail 84441 invoked by uid 500); 21 Aug 2018 13:57:02 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 84376 invoked by uid 99); 21 Aug 2018 13:57:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2018 13:57:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2DA38180659 for ; Tue, 21 Aug 2018 13:57:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id wZTDna9hkqjO for ; Tue, 21 Aug 2018 13:57:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id EE81A5F49F for ; Tue, 21 Aug 2018 13:57:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6F1F2E04AD for ; Tue, 21 Aug 2018 13:57:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 22DC02469B for ; Tue, 21 Aug 2018 13:57:00 +0000 (UTC) Date: Tue, 21 Aug 2018 13:57:00 +0000 (UTC) From: "Evgeny Kraynov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IGNITE-4845) REST LOG API does not work when Ignite-log4j module is enabled MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-4845?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D165= 87464#comment-16587464 ]=20 Evgeny Kraynov edited comment on IGNITE-4845 at 8/21/18 1:56 PM: ----------------------------------------------------------------- Log command of the REST API provides access just for logs of the node where= the service raised.=C2=A0=20 Logs can be retrieved from IGNITE_HOME/ or from the path defined in the lo= g configuration of the node. Log configuration should be defined expliciltly when Ignite-log4j module i= s enabled. =C2=A0 XML: =C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 ... =C2=A0 =C2=A0Java: IgniteConfiguration cfg =3D new IgniteConfiguration(); IgniteLogger log =3D new Log4JLogger("log4j.xml"); cfg.setGridLogger(log); =C2=A0 In this way, Log command will provide by default (without Path parameter) = logs from the file specified=20 in=C2=A0 log4j.xml =C2=A0 I think, the current behavior is correct was (Author: evgenk900): Log command of the REST API provides access just for logs of the node where= the service raised.=C2=A0=20 Logs can be retrieved from IGNITE_HOME/ or from the path defined in the log= configuration of the node. Log configuration should be defined expliciltly when Ignite-log4j module is= enabled. =C2=A0 XML: =C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 ... =C2=A0 =C2=A0 Java: IgniteConfiguration cfg =3D new IgniteConfiguration(); IgniteLogger log =3D new Log4JLogger("log4j.xml"); cfg.setGridLogger(log); =C2=A0 In this way, Log command will provide by default (without Path parameter) l= ogs from the file specified=20 in=C2=A0 log4j.xml =C2=A0 I think, the current behavior is correct > REST LOG API does not work when Ignite-log4j module is enabled > -------------------------------------------------------------- > > Key: IGNITE-4845 > URL: https://issues.apache.org/jira/browse/IGNITE-4845 > Project: Ignite > Issue Type: Bug > Components: clients > Affects Versions: 1.8 > Reporter: Sam > Priority: Minor > Labels: newbie > > For security reason Ignite should internally figure out which log file to= read so Path parameter does not make sense.=20 > Ignite-log4j module is enabled simply including this jar file, now it use= s my application log4j configuration to log successfully. But ignite.log() = is never initialized, it is null, hence REST API not able to figure out whe= re is the log file.=20 > enforcing either of below workaround works -=20 > 1. Log file location need to start with IGNITE_HOME and use Path paramete= r in LOG command.=20 > 2. Enforce logging into IGNITE_HOME/work/log/ignite.log location.=20 > when Ignite-log4j module is enabled it should make Ignite aware of loggin= g configuration.=20 > More details @ [http://apache-ignite-users.70518.x6.nabble.com/REST-servi= ce-command-LOG-td10148.html#a11158] -- This message was sent by Atlassian JIRA (v7.6.3#76005)