You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Sam (JIRA)" <ji...@apache.org> on 2017/03/20 20:53:41 UTC
[jira] [Created] (IGNITE-4845) REST LOG API does not work when
Ignite-log4j module is enabled
Sam created IGNITE-4845:
---------------------------
Summary: 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: rest
Affects Versions: 1.8
Reporter: Sam
Priority: Minor
Fix For: 2.0
For security reason Ignite should internally figure out which log file to read so Path parameter does not make sense.
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.
enforcing either of below workaround works -
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.
when Ignite-log4j module is enabled it should make Ignite aware of logging configuration.
More details @ [http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-td10148.html#a11158]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)