JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report JPPF-615  -  ProcessLauncher should not explicitely rely on Log4j for logging
Posted Jan 10, 2020 - updated Jan 17, 2020
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    Closed
  • Assigned to
     lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Other
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Reproducability
    Always
  • Severity
    Normal
  • Targetted for
    icon_milestones.png JPPF 6.1.5
Issue description
The ProcessLauncher class is used to launch drivers and nodes and allows them to be restarted remotely. We have found here that it always sets the "log4j.configuration" system property, even if the value of the property is null, which may happen if another logging framework is used. This results in an error being printed at startup.
Steps to reproduce this issue
Start a node or driver without specifiying "-Dlog4j.configuration=/path/to/log4j.properties"