log4j experiments

2 loggers into 2 different files :


log = C:/Apache24/htdocs/logs

log4j.rootLogger=TRACE, 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 [%24F:%t:%L] - %m%n

log4j.appender.debugLog=org.apache.log4j.FileAppender
log4j.appender.debugLog.File=${log}/debug.html
log4j.appender.debugLog.layout=org.apache.log4j.HTMLLayout
log4j.appender.debugLog.layout.Title=HTML Debug
log4j.appender.debugLog.layout.LocationInfo=true

log4j.appender.reportsLog=org.apache.log4j.FileAppender
log4j.appender.reportsLog.File=${log}/reports.html
log4j.appender.reportsLog.layout=org.apache.log4j.HTMLLayout
log4j.appender.debugLog.layout.Title=HTML Reports
log4j.appender.debugLog.layout.LocationInfo=true

log4j.category.debugLogger=TRACE, debugLog
log4j.additivity.debugLogger=false

log4j.category.reportsLogger=DEBUG, reportsLog
log4j.additivity.reportsLogger=false


And use this by:

static final Logger debugLog = Logger.getLogger("debugLogger");
static final Logger resultLog = Logger.getLogger("reportsLogger");


debugLog.debug("This is a debug level log entry in a debug log");
debugLog.info("This is an info level log entry in a debug log");
debugLog.warn("This is a warn level log entry in a debug log");
debugLog.error("This is an error level log entry in a debug log");
debugLog.fatal("This is a fatal level log entry in a debug log");
debugLog.trace("This is a trace level log entry in a debug log");

resultLog.debug("This is a debug level log entry in a result log");
resultLog.info("This is an info level log entry in a result log");
resultLog.warn("This is a warn level log entry in a result log");
resultLog.error("This is an error level log entry in a result log");
resultLog.fatal("This is a fatal level log entry in a result log");
resultLog.trace("This is a trace level log entry in a result log");



1 logger into 2 different files based on appender config:

log = C:/Apache24/htdocs/logs

log4j.rootLogger=TRACE, consoleApender, LogA, LogB

#Console Appender
log4j.appender.consoleApender=org.apache.log4j.ConsoleAppender
log4j.appender.consoleApender.Target=System.out  
log4j.appender.consoleApender.layout=org.apache.log4j.PatternLayout
log4j.appender.consoleApender.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n

#LogA Appender
log4j.appender.LogA=org.apache.log4j.FileAppender
log4j.appender.LogA.File=${log}/LogA.html
log4j.appender.LogA.layout=org.apache.log4j.HTMLLayout
log4j.appender.LogA.layout.LocationInfo=true

#LogB Appender
log4j.appender.LogB=org.apache.log4j.FileAppender
log4j.appender.LogB.File=${log}/LogB.html
log4j.appender.LogB.layout=org.apache.log4j.HTMLLayout
log4j.appender.LogB.layout.LocationInfo=true

# Set the logger level of File Appender to WARN
log4j.appender.LogA.Threshold = ERROR
log4j.appender.LogB.Threshold = debug


static final Logger rootLogger = Logger.getLogger(MISLoginController.class);

rootLogger.debug("This is a debug level log entry in a debug log");
rootLogger.info("This is an info level log entry in a debug log");
rootLogger.warn("This is a warn level log entry in a debug log");
rootLogger.error("This is an error level log entry in a debug log");
rootLogger.fatal("This is a fatal level log entry in a debug log");
rootLogger.trace("This is a trace level log entry in a debug log");


Comments

Post a Comment

Popular posts from this blog

WIKIPEDIA API and ChatBots

I have been trying to use ontological bases in my chatbot to introduce interactivity which can take the conversation forward. What I have till now : Any user query is parsed by an NLP engine to classify if the intent is any one of the preset intents. Some of these preset intents are greetings, compliments, tasks assigned in the Talentify for Business app amongst a few. If none of the intents are matched then the user query is passed in sequence to various search engines and their web results are scraped to get a metadata response generated by the search engine, which usually is a representation of the internal knowledge graph of the search engine implementation. If none of the search engines can identify that query, then the query is passed to a knowledge engine called wolfram alpha which in most of the cases can give response to even very complex queries like "what is the distance between Chennai and Bangalore in kilometres" If even that fails then a default random...
Read more

SPARQL

Sparql can be used to query structured data sets like DBPedia. These queries can be run on SPAQL enpoints like http://lod.openlinksw.com/sparql or http://dbpedia.org/sparql/. The queries can be slightly different, but for an experienced SPARQLer (which I hope to be one day) this won't be a problem. Here are a few of my first queries, the structure will be purpose followed by the query: The urban and metro population of Patna PREFIX dbo: <http://dbpedia.org/ontology/> PREFIX dbr: <http://dbpedia.org/resource/> select ?populationUrban  ?populationMetro where {   dbpedia:Patna  dbo:populationUrban ?populationUrban;                  dbo:populationMetro ?populationMetro  . } Details of Hemmingway: prefix dbpedia: <http://dbpedia.org/resource/> prefix dbpedia-owl: <http://dbpedia.org/ontology/> select ?abstract ?thumbnail where {    dbpedia:Ernest_Hemingway ...
Read more

Wikipedia API

A collection of a number of wikipedia API links to perform a plethora of tasks: Searching : Search can be done using Opensearch or query on the api Open search method: Use url:  https://en.wikipedia.org/w/api.php?action=opensearch&search=concurrency+java&limit=10&namespace=0&format=json https : //en.wikipedia.org/w/api.php ? action = opensearch & search = zyz # search query & limit = 1 # return only the first result & namespace = 0 # search only articles, ignoring Talk, Mediawiki, etc. & format = json # jsonfm prints the JSON in HTML for debugging. Query method: Use url: https://en.wikipedia.org/w/api.php?action=query&list=search&srsearch=what+is+concurrency+java&utf8=&format=json   Titles : Once the search yields url (in case of opensearch) or titles in case of query search, each can be individually opened. In case of query search, plain text or w-test can be obtained using...
Read more