Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
Date: Mon, 13 Mar 2017 17:57:16 -0700 (MST)
From: "javastuff.sam@gmail.com" <javastuff.sam@gmail.com>
To: user@ignite.apache.org
Message-ID: <1489453036837-11158.post@n6.nabble.com>
In-Reply-To: <1484953128003-10164.post@n6.nabble.com>
References: <1484857266893-10148.post@n6.nabble.com> <1484937343559-10159.post@n6.nabble.com> <1484939544179-10160.post@n6.nabble.com> <1484953128003-10164.post@n6.nabble.com>
Subject: Re: REST service command LOG
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Tue, 14 Mar 2017 00:57:21 -0000

Hi Val,

Apologies for coming back to this thread late.

I agree for security reasons it should internally figure out which log file
to read. However it does not work, here is the scenario -

Ignite-log4j module is enabled simply including this jar file, now it uses
my application log4j configuration to log successfully. But ignite.log() is
never initialized, it is null, hence REST API not able to figure out where
is the log file. 
I have to enforce either of the workaround - 
1. Log file location need to start with IGNITE_HOME and use Path parameter
in LOG command.
2. Enforce logging into IGNITE_HOME/work/log/ignite.log location.

I think when Ignite-log4j module is enabled it should make Ignite aware of
logging configuration. 

Thanks,
-Sam


--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-tp10148p11158.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.