Scroll
Request A Demo

4 Radnor Corporate Center
Suite 350
Radnor, PA 19087

+1 (888) 507-2270

log4j Warnings Messages

b Barry
 on January 9, 2014

 

I've recently installed the OpenCDISC Validator tool (v1.4.1) on a Red Hat Linux server.   The Linux server has Java 1.7.0_25 installed.  Using Exceed, I was able to start the GUI user interface with the command "java -Xms256m -Xmx1024m -jar lib/validator-gui-1.4.1.jar".  I executed a job and generated the report.  I didn't see any messages in the UI.  However, I noticed in the terminal window. where I launched the java command above, 3 warning messages:

log4j:WARN No appenders could be found for logger (org.opencdisc.validator.data.SasTransportDataSource).

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

 

The software seems to be complaining that it cannot find the files "log4j.properties" and "log4j.xml".  I can't find these anywhere in the system.  A google search implies that these are files I need to create (http://www.mkyong.com/logging/log4j-log4j-properties-examples/) and http://howtodoinjava.com/2013/04/08/how-to-configure-log4j-using-properties-file/

 

Thoughts? 

Thanks,

Barry A.

Forums: Troubleshooting and Problems

m Michael
on January 9, 2014

Go to your opencdisc-validator\lib\properties directory

 In it you will find a file callled logback.xml.   this controls logging.

You should also have the following 3 .jars in your opencdisc-validator\lib directory.   These are the libraries for Log4j and http://www.slf4j.org/

 

  1. slf4j-api-1.7.5.jar
  2. slf4j-log4j12-1.7.5.jar
  3. log4j-1.2.16.jar

 

b Barry
on January 9, 2014

Thanks, I found all of these files.  The logback.xml was in the opencdisc-validator/lib/properties folder and the 3 jar files in the opencdisc-validator/lib folder. 

m Michael
on January 9, 2014

And you still get the warning messages with version 1.4.1 right ?  if so, this is not an issue for the customer unless an error occurs and you want it logged (the GUI will always bubble up the error though).   Of course, no one likes to see junk in their output, so create a file called lib\properties\log4j.properties with text below, then rerun.   that will fix the problem.   We changed logging internally in version 1.4.1 for better integration with OpenCDISC Enterprise.   Enterprise hides all these configuration issues from the client.  

 

log4j.rootLogger=WARN, default

log4j.rootLogger.org.opencdisc.validator.data.SasTransportDataSource = ERROR

log4j.rootLogger.org.opencdisc.validator.engine.BlockValidator = ERROR

log4j.rootLogger.org.opencdisc.validator.settings.ConfigurationManager = ERROR

log4j.appender.default=org.apache.log4j.ConsoleAppender

log4j.appender.default.layout=org.apache.log4j.PatternLayout

log4j.appender.default.layout.ConversionPattern=%-5p |%-4t |%-60c |%4L |%m%n

b Barry
on January 9, 2014

Thanks Mike, adding that file worked.  Does this mean I need to add this file each time a new version of the tool is released?

 

m Michael
on January 9, 2014

We should be including this file in each release.  I will put a note to do so for future releases.   For now, keep it handy.  

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.

I Agree
close

Request A Demo

* Required Field

Fill out my online form.