Skip to main content

iBatis and Log4j


  1. log4j.rootLogger=DEBUG, A2  
  2. # SqlMap logging configuration...  
  3. log4j.logger.com.ibatis=DEBUG  
  4. log4j.logger.com.ibatis.common.jdbc.SimpleDataSource=DEBUG  
  5. log4j.logger.com.ibatis.common.jdbc.ScriptRunner=DEBUG  
  6. log4j.logger.com.ibatis.sqlmap.engine.impl.SqlMapClientDelegate=DEBUG  
  7. log4j.logger.java.sql.Connection=DEBUG  
  8. log4j.logger.java.sql.Statement=DEBUG  
  9. log4j.logger.java.sql.PreparedStatement=DEBUG  
  10. log4j.logger.java.sql.ResultSet=DEBUG  
  11. # Console output...  
  12. log4j.appender.stdout=org.apache.log4j.ConsoleAppender  
  13. log4j.appender.stdout.layout=org.apache.log4j.PatternLayout  
  14. log4j.appender.stdout.layout.ConversionPattern=%5p [%t] - %m%n  
  15.    
  16. log4j.appender.A2=org.apache.log4j.FileAppender  
  17. log4j.appender.A2.File=C:/dcsi/twacs.log  
  18. # Truncate 'twacs' if it aleady exists.  
  19. log4j.appender.A2.Append=true  
  20.    
  21. # Appender A2 uses the PatternLayout.  
  22. log4j.appender.A2.layout=org.apache.log4j.PatternLayout  
  23. log4j.appender.A2.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c %x - %m%n  
  24. #log4j.appender.A2.layout.ConversionPattern=%-5r %-5p [%t] %c{2} - %m%n  
Labels:

Comments

Post a Comment

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold  highlighted in example below) which resolve the problems.   example: <band height="20" splitType="Stretch" > <textField isStretchWithOverflow="true" pa...
4 comments
Read more

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for c...
1 comment
Read more

JasperReports - Configuration Reference

Data Source / Query Executer net.sf.jasperreports.csv.column.names.{arbitrary_name} net.sf.jasperreports.csv.date.pattern net.sf.jasperreports.csv.encoding net.sf.jasperreports.csv.field.delimiter net.sf.jasperreports.csv.locale.code net.sf.jasperreports.csv.number.pattern net.sf.jasperreports.csv.record.delimiter net.sf.jasperreports.csv.source net.sf.jasperreports.csv.timezone.id net.sf.jasperreports.ejbql.query.hint.{hint} net.sf.jasperreports.ejbql.query.page.size net.sf.jasperreports.hql.clear.cache net.sf.jasperreports.hql.field.mapping.descriptions net.sf.jasperreports.hql.query.list.page.size net.sf.jasperreports.hql.query.run.type net.sf.jasperreports.jdbc.concurrency net.sf.jasperreports.jdbc.fetch.size net.sf.jasperreports.jdbc.holdability net.sf.jasperreports.jdbc.max.field.size net.sf.jasperreports.jdbc.result.set.type net.sf.jasperreports.query.chunk.token.separators net.sf.jasperreports.query.executer.factory.{language} net.sf.jasperreports.xpath....
Post a Comment
Read more