Log4j output not displayed in Eclipse console

Question

For some reason my Eclipse console no longer displays Log4j INFO and DEBUG statements when I run JUnit tests  In terms of code there hasn t been any change  so it must something to do with the Eclipse configuration   All I do in my Unit test is the following and for some reason ONLY the ERROR statement is displayed in the Eclipse console  Why  Where shall I look for clues   public class SampleTest      private static final Logger LOGGER   Logger getLogger SampleTest class        Before    public void init   throws Exception                Log4J junit configuration         BasicConfigurator configure            LOGGER info  INFO TEST           LOGGER debug  DEBUG TEST           LOGGER error  ERROR TEST             Details    log4j-1 2 6 jar junit-4 6 jar Eclipse IDE for Java Developers  Version  Helios Release  Build id  20100617-1415

User · Answer

Thought this was a genuine defect but it turns out that my console size was limited, and caused the old content past 80000 characters to be cut off.

Right click on the console for the preferences and increase the console size limit.

User · Answer

Check for log4j configuration files in your output  i e  bin or target classes  directory or within generated project artifacts   jar  war  ear   If this is on your classpath it gets picked up by log4j

User · Answer

The Eclipse Console Window has a Filter Property  in some cases only system err is active     Rigt click into Eclipse console window -  Preferences -  Console and ensure that checkbox   Show when Program writes to standard out   is active   Alternatively you can configure log4j to write alway to System err like this    lt  xml version  1 0  encoding  UTF-8    gt   lt  DOCTYPE log4j configuration SYSTEM  log4j dtd  gt   lt log4j configuration xmlns log4j  http   jakarta apache org log4j   gt       lt appender name  AppConsole  class  org apache log4j ConsoleAppender  gt           lt param name  Target  value  System err    gt           lt param name  Encoding  value  ISO-8859-15    gt           lt layout class  org apache log4j PatternLayout  gt               lt param name  ConversionPattern                  value   d dd MM yyyy HH mm ss   5p kontext  c 1   L -  m n    gt           lt  layout gt       lt  appender gt       lt root gt           lt level value  debug    gt           lt appender-ref ref  AppConsole    gt       lt  root gt   lt  log4j configuration gt

User · Answer

Check your log4j properties file  Check easy example here at here

User · Answer

Go to Run configurations in your eclipse then -VM arguments add this  -Dlog4j configuration log4j-config folder log4j xml   replace log4j-config folder with your folder structure where you have your log4j xml file

User · Answer

I had the same error   I am using Jboss 7 1 AS  In the configuration file - standalone xml edit the following tag    stop your server and edit         lt root-logger gt               lt level name  ALL   gt               lt handlers gt                   lt handler name  CONSOLE   gt                   lt handler name  FILE   gt               lt  handlers gt       lt  root-logger gt    The ALL has the lowest possible rank and is intended to turn on all logging

User · Answer

Configuring with BasicConfigurator configure    sets up a basic console appender set at debug  A project with the setup above and no other code  except for a test  should produce three lines of logging in the console  I cannot say anything else than  it works for me    Have you tried creating an empty project with just log4j and junit  with only the code above and ran it   Also  in order to get the  Beforemethod running    Test public void testname   throws Exception       assertTrue true       EDIT   If you run more than one test at one time  each of them will call init before running   In this case  if you had two tests  the first would have one logger and the second test would call init again  making it log twice  try it  - you should get 9 lines of logging in console with two tests   You might want to use a static init method annotated with  BeforeClass to avoid this  Though this also happens across files  you might want to have a look at documentation on TestSuites in JUnit 4  And or call BasicConfigurator resetConfiguration    in an  AfterClass annotated class  to remove all loggers after each test class   test suite   Also  the root logger is reused  so that if you set the root logger s level in a test method that runs early  it will keep this setting for all other tests that are run later  even if they are in different files   will not happen when resetting configuration    Testcase - this will cause 9 lines of logging   import static org junit Assert assertTrue   import org apache log4j BasicConfigurator  import org apache log4j Logger  import org junit Before  import org junit Test   public class SampleTest      private static final Logger LOGGER   Logger getLogger SampleTest class        Before    public void init   throws Exception                Log4J junit configuration         BasicConfigurator configure              Test     public void testOne   throws Exception          LOGGER info  INFO TEST           LOGGER debug  DEBUG TEST           LOGGER error  ERROR TEST            assertTrue true              Test    public void testTwo   throws Exception          LOGGER info  INFO TEST           LOGGER debug  DEBUG TEST           LOGGER error  ERROR TEST            assertTrue true            Changing the init method reduces to the excepted six lines    BeforeClass public static void init   throws Exception          Log4J junit configuration      BasicConfigurator configure        Your problem is probably caused in some other test class or test suite where the logging level of the root logger is set to ERROR  and not reset   You could also test this out by resetting in the  BeforeClass method  before setting logging up   Be advised that these changes might break expected logging for other test cases until it is fixed at all places  I suggest trying out how this works in a separate workspace project to get a feel for how it works

User · Answer

Add a test dependency to your pom to slf4j            lt dependency gt               lt groupId gt org slf4j lt  groupId gt               lt artifactId gt slf4j-simple lt  artifactId gt               lt version gt   slf4j version  lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt

User · Answer

A simple log4j properties file can look like this   log4j rootCategory debug console  log4j appender console org apache log4j ConsoleAppender log4j appender console target System out log4j appender console immediateFlush true log4j appender console encoding UTF-8 log4j appender console threshold info  log4j appender console layout org apache log4j PatternLayout log4j appender console layout conversionPattern  d   t   -5p  c -  m n   Place it in your class path  target classes folder   Or you if you have a Maven project  place it under your src main resources and Eclipse will copy it to your class path   Without a configuration file  you should see an Eclipse warning in the console like this   log4j WARN No appenders could be found for logger  log4j WARN Please initialize the log4j system properly

User · Answer

if the log4j xml file is not in the project and you are using tomcat  try going to tomcat instance and search for log4j  Try changing the consoleAppender level to debug and redeploy the application in tomcat  That might help

User · Answer

Makes sure when running junit test cases  you have the log4j properties or log4j xml file in your test resources folder

User · Answer

Check that your log4j properties or log4j xml are copied to your IDE classpath and loads when calling BasicConfigurator configure

User · Answer

There is a case I make  exception happen in somewhere  but I catched the exception without print anything  thus the code didn t even reach the log4j code  so no output

User · Answer

I once had an issue like this  when i downloadad a lib from Amazon  for Amazon webservices  and that jar file contained a log4j properties and somehow that was used instead of my good old  self configed log4j  Worth a check

User · Answer

My situation was solved by specifing the VM argument to the JAVA program being debugged  I assume you can also set this in  eclipse ini file aswell

User · Answer

Sounds like log4j picks up another configuration file than the one you think it does   Put a breakpoint in log4j where the file is opened and have a look at the files getAbsolutePath

User · Answer

One thing to note  if you have a log4j properties file on your classpath you do not need to call BasicConfigurator   A description of how to configure the properties file is here   You could pinpoint whether your IDE is causing the issue by trying to run this class from the command line with log4j jar and log4j properties on your classpath

User · Answer

Look in the log4j properties or log4j xml file for the log level  It s probably set to ERROR instead of DEBUG

[java] Log4j output not displayed in Eclipse console

Examples related to java

Examples related to eclipse

Examples related to junit

Examples related to log4j