log4j

问题 I have a Spring Application which is using JPA/Hibernate. I want to track every insert and update statement in the DB. Is it possible to log the data update to a file and output a new file everyday. Basically if something changes in the database I want to track it in a log file. And there needs to be one log file everyday. I do have log4.xml in my application. Besides this I dont know where to begin. Any suggestions. tips solutions and pointers to good references are greatly appreciated. 回答1:

问题 We are using log4j2 extensively in our system, and configures it with log4j2.xml . Now I need a new app that run jobs , and I want to separately capture all the logs resulted between time X and Y and put it in a database. Normal logging from our framework should occur as usual (to files or wherever log4j2.xml points to), But from time X to time Y. I also want all the logging should be captured, preferably to a list of strings or something that can be saved in a database table. My idea is to

问题 I have come across an odd problem, which I do not understand: when I remove my File appender it prevents me logging to my server, even though the File appender should not be responsible for logging anything to the server; that task should only be for my GELF appender. The following code is able to log both to my console and server just fine Java import org.apache.logging.log4j.LogManager; import org.apache.logging.log4j.Logger; public class App { private static final Logger log4j = LogManager

问题 In our logs we're seeing credit-card numbers due to people hitting some of the ULRs in our app with CC info (I have no idea why they are doing this). We want to sanitize this information (because of PCI considerations) and not even persist it to disk. Hence, I want to be able to sanitize the log entry before it hits the log file. I've been looking at Tomcat Valves (Access Log Valve). Is this the way to go? 回答1: I was able to solve this problem by extending AccessLogValve and overriding public

问题 Following is my log4j.properties: log4j.rootLogger=ALL, stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.Target=System.out log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d [%t] %p [%c] - %m%n log4j.logger.org.springframework=ALL log4j.logger.app.dev.ems=ALL log4j.logger.org.springframework.transaction=ALL I have mentioned the log4jConfigLocation in the web.xml: <context-param> <param-name

问题 Based on the following configuration i am expecting my log4j should write to HDFS folder (/myfolder/mysubfolder). But it's not even creating a file with the given name hadoop9.log. I tried by creating hadoop9.log manually on hdfs. Still it didn't work. Am i missing anything in log4j.properties.? # Define some default values that can be overridden by system properties hadoop.root.logger=INFO,console,RFA,DRFA hadoop.log.dir= /myfolder/mysubfolder hadoop.log.file=hadoop9.log # Define the root

问题 I am trying to use commons logging and want to use java.util.logging as underlying mechanism. LogTest.java import org.apache.commons.logging.*; public class LogTest { public static void main(String args[]) { System.setProperty("java.util.logging.config.file","log.properties"); Log logger = LogFactory.getLog(LogTest.class); logger.trace("trace msg"); } } I have src/main/resources/log.properties ( I am using maven project ) handlers=java.util.logging.ConsoleHandler # Default global logging

问题 Adding log4j [1] in tomcat 6.0.x forces tomcat to produce logs in "catalina" file. However, the default catalina.out is still produced and populated with logs. So, questions: Is it safe to delete catalina.out file (while server running)? If yes, could this deletion be added to tomcat startup script? If yes, could anyone please point out the file and the required script? Is it possible for tomcat to stop createing the catalina.out, since it is not nessesary anymore? http://tomcat.apache.org

问题 (Note that it's more of a Bash question than a Java question, see note below) When configuring log4j in each class, we do the following: public class Example { private static final Logger log = Logger.getLogger( Example.class ); The problem is that we now have a medium-sized codebase (200K LOC) containing a lot of Java classes and... Quite some misconfigured log4j loggers. It's because people (including me, I admit), did silly cut'n'paste resulting sometimes in this: public class Another {

问题 I deploy multiple applications (ear) in one domain on a Weblogic-Server. Each application uses log4j. My wish is to configure each applications with its own log4j.xml. Is this possible? The log4j.xml should be outside of the ear, so that I can edit it without rebuilding the ear. I'm used to put the log4j.xml in the serverclasspath, then it is read on server startup. But then I don't have the possibility to use different log4j.xml for each application. I think it is a classpath issue, because