log4j

问题 Basically, when using log4j, I know we have to initiate a Logger by using Logger.getLogger(MyClass.class) or Logger.getLogger("MyClass"). I have too many classes and I dont want to add this statement in every class. Rather, what I woudl like to do is this Logger.info(this,"My message"); Where Logger is a class I have written (not the one in log4j) which in turn initiates an object of type Logger (org.apache.log4j.Logger) and carries on with the message. This is my Logger.java package com

问题 My app only starts logging to log4j if I put a : on the end off the classpath. I already have the properties file and the jar in the classpath, so I'm not sure what's going on. What does ending the classpath with a colon even do? The startup command thus becomes something like this: java -cp path-to-log4j.properties:bunch:of:other:stuff: app If I take that last colon off it stops logging, as if it can't find log4j. My question is, what is that last colon actually doing, as in what directory

问题 I'm having a problem where logging works correctly when I run tomcat in non-forked mode from grails, but does not work correctly in forked mode. Here is my Log4j configuration: Config.groovy : // log4j configuration log4j = { appenders { file name:"fileLogger", file: "c:/logs/app-log.log", threshold: Level.DEBUG } debug fileLogger: ['com.foo', 'BootStrap'] info fileLogger: ['org.springframework'] error fileLogger: [ 'org.codehaus.groovy.grails.web.servlet', // controllers 'org.codehaus.groovy

问题 We have about 19 applications in our weblogic 8.1 server. Each application is an .Ear application with a few ejbs, mdb etc., Each application has a log4j properties defined in a .properties file somewhere in the filesystem. We keep getting this error(below) in the server logs for all the applications. This exception is not caught in the application, the flow of the application does not stop, but we miss a log statement or two when this exception occurs. log4j:ERROR Attempted to append to

问题 I am migrating to Logback from log4j. Log4j has the %l format specifier which will print out the fully qualified name of the calling method followed by the callers source the file name and line number between parentheses. Example: com.my.company.MyClass.doSomething(MyClass.java:54) I want the same output using Logback. They don't have the %l format specified. They do have the %caller format specifier and when you provide the {0} option you will get the first level of the call stack. Example:

问题 I can make the log to go the console but I cant seem to make it go to a log file. Here is my properties file. log4j.rootLogger=DEBUG, LOG , stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%5p %d{d/MM/yy HH:mm:ss}:%m%n # log4j.appender.LOG.Threshold=INFO log4j.appender.LOG=org.apache.log4j.RollingFileAppender log4j.appender.LOG.File=C:\dev\harry\data\logs\core.log log4j

问题 I'm running an Oozie Java workflow (the jar file is in HDFS), and I'd like to add logging functionality to my application. Does anybody know how to do it? Where should I put my "log4j.properties" file? How can I make log4j to output the log to a location in HDFS? 回答1: Looking in this documentation, you can try adding oozie-log4j.properties in your oozie directory (where workflow.xml is). Here are the default settings: log4j.appender.oozie=org.apache.log4j.rolling.RollingFileAppender log4j

问题 Do any of the popular Java logging frameworks support a rolling file appender, that I can configure to rollover daily, and also delete any log file that is over some number of days old? I know I could use a rolling file appender and a cron, but was wondering if anyone knew of an appender that can do both. 回答1: Logback's classic RollingFileAppender provides this and more. An example configuration from the manual (http://logback.qos.ch/manual/appenders.html#onRollingPolicies) <configuration>

问题 How can I enable Log4j for jetty-maven-plugin 9? I followed the Jetty documentation for standalone Jetty 9 and added JARs and property file. Jetty configuration: <plugin> <groupId>org.eclipse.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <version>9.0.5.v20130815</version> <configuration> <webApp> <contextPath>/mywebapp</contextPath> <jettyEnvXml>jetty-env.xml</jettyEnvXml> </webApp> <systemProperties> <systemProperty> <name>log4j.configuration</name> <value>log4j-jetty

问题 Does anyone see why this log is not writing to file. It is writing to standard out twice but not to the file: Also, I tried removing the "Stdout" appender and then I don't get any logging at all. package org.berlin.wicket; import org.apache.log4j.Logger; private static final Logger LOG = Logger.getLogger(QuickstartPage.class); LOG.info("Loading constructor"); log4j.rootLogger=DEBUG,Stdout,mainAppender log4j.appender.Stdout=org.apache.log4j.ConsoleAppender log4j.appender.Stdout.layout=org