Terrier Core

Terrier breaks existing log4j configuration

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Trivial Trivial
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 4.0
  • Component/s: None

Issue Links

Activity

Hide
Craig Macdonald added a comment - 06/Apr/10 6:14 PM

Nice catch. I have seen this in Hadoop where the logging changes once Terrier is started.

Show
Craig Macdonald added a comment - 06/Apr/10 6:14 PM Nice catch. I have seen this in Hadoop where the logging changes once Terrier is started.
Hide
Craig Macdonald added a comment - 25/May/10 12:09 PM

I tried both these solutions, and it prevented the Terrier log4j configuration from being loaded.

Show
Craig Macdonald added a comment - 25/May/10 12:09 PM I tried both these solutions, and it prevented the Terrier log4j configuration from being loaded.
Hide
Craig Macdonald added a comment - 30/Mar/11 11:30 PM

Tagging for 3.1, will see if I can find a solution.

Show
Craig Macdonald added a comment - 30/Mar/11 11:30 PM Tagging for 3.1, will see if I can find a solution.
Hide
Craig Macdonald added a comment - 04/Apr/11 12:08 PM

Gave a bit more look at this. The issue is that the Hadoop configuration is loaded before ApplicationSetup, hence the default loggers are normally:

[org.apache.log4j.ConsoleAppender@43684706, org.apache.hadoop.metrics.jvm.EventCounter@730efd7c]
Show
Craig Macdonald added a comment - 04/Apr/11 12:08 PM Gave a bit more look at this. The issue is that the Hadoop configuration is loaded before ApplicationSetup, hence the default loggers are normally:
[org.apache.log4j.ConsoleAppender@43684706, org.apache.hadoop.metrics.jvm.EventCounter@730efd7c]

People

Dates

  • Created:
    06/Apr/10 6:06 PM
    Updated:
    17/Jun/11 1:03 PM