Re: [jira] Resolved: (NUTCH-303) logging improvements
That's a good news. Sami, I have not made changes to web2. Do you want that I switch web2 to Commons Logging? I am allready working with it and unfortunately facing some classloading issues. Hopefully the solution will come up sooner than later. -- Sami Siren
Re: [jira] Resolved: (NUTCH-303) logging improvements
There seems to be two log4j.properties files in generated war, is this intentional? However it works just fine. jar -tf nutch-0.8-dev.war |grep log4j.properties WEB-INF/classes/log4j.properties WEB-INF/classes/log4j.properties -- Sami Siren Jerome Charron (JIRA) wrote: [ http://issues.apache.org/jira/browse/NUTCH-303?page=all ] Jerome Charron resolved NUTCH-303: -- Resolution: Fixed Nutch now uses the Commons Logging API and log4j as the default implementation. There is 3 log4j.properties configuration files: 1. conf/log4j.properties used by the back-end. It uses by default the Daily Rolling File Appender. By default, the logging file is located in $NUTCH_HOME/logs/nutch.log Another location can be specified by using env. variables $NUTCH_LOG_DIR and $NUTCH_LOGFILE. 2. src/web/log4j.properties used by the front-end container. It uses by default the Console Appender. 3. srr/test/log4j.properties used by unit tests It uses by default the Console Appender. I have tested this patch on both front-end / back-end and unit tests env. But please notice, that I have only one box available = I just tested it on mono-deployment env. logging improvements Key: NUTCH-303 URL: http://issues.apache.org/jira/browse/NUTCH-303 Project: Nutch Type: Improvement Versions: 0.8-dev Reporter: Jerome Charron Assignee: Jerome Charron Priority: Minor Fix For: 0.8-dev Switch to the apache commons logging facade. See HADOOP-211 and following thread http://www.mail-archive.com/nutch-developers%40lists.sourceforge.net/msg08706.html
Re: [jira] Resolved: (NUTCH-303) logging improvements
There seems to be two log4j.properties files in generated war, is this intentional? Not intentional. A side effect. In fact, the first one is the one that comes from conf dir (I will exlude it in war so that it will be clearier). The second one (that override the first one) is the good one that comes from web directory. However it works just fine. That's a good news. Sami, I have not made changes to web2. Do you want that I switch web2 to Commons Logging? Regards Jérôme -- http://motrech.free.fr/ http://www.frutch.org/
[jira] Resolved: (NUTCH-303) logging improvements
[ http://issues.apache.org/jira/browse/NUTCH-303?page=all ] Jerome Charron resolved NUTCH-303: -- Resolution: Fixed Nutch now uses the Commons Logging API and log4j as the default implementation. There is 3 log4j.properties configuration files: 1. conf/log4j.properties used by the back-end. It uses by default the Daily Rolling File Appender. By default, the logging file is located in $NUTCH_HOME/logs/nutch.log Another location can be specified by using env. variables $NUTCH_LOG_DIR and $NUTCH_LOGFILE. 2. src/web/log4j.properties used by the front-end container. It uses by default the Console Appender. 3. srr/test/log4j.properties used by unit tests It uses by default the Console Appender. I have tested this patch on both front-end / back-end and unit tests env. But please notice, that I have only one box available = I just tested it on mono-deployment env. logging improvements Key: NUTCH-303 URL: http://issues.apache.org/jira/browse/NUTCH-303 Project: Nutch Type: Improvement Versions: 0.8-dev Reporter: Jerome Charron Assignee: Jerome Charron Priority: Minor Fix For: 0.8-dev Switch to the apache commons logging facade. See HADOOP-211 and following thread http://www.mail-archive.com/nutch-developers%40lists.sourceforge.net/msg08706.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
