Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-4845

REST LOG API does not work when Ignite-log4j module is enabled

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not A Problem
    • Affects Version/s: 1.8
    • Fix Version/s: None
    • Component/s: clients
    • Labels:

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              javastuff.sam@gmail.com Sam
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: