IN PROGRESS - issue BATCH-262: Hibernate Job blocks on flush
http://jira.springframework.org/browse/BATCH-262 Revert to less verbose logging
This commit is contained in:
@@ -14,8 +14,8 @@ log4j.appender.chainsaw.layout=org.apache.log4j.xml.XMLLayout
|
||||
|
||||
### set log levels - for more verbose logging change 'info' to 'debug' ###
|
||||
|
||||
# log4j.rootLogger=info, stdout
|
||||
log4j.rootLogger=info, stdout, chainsaw
|
||||
log4j.rootLogger=info, stdout
|
||||
# log4j.rootLogger=info, stdout, chainsaw
|
||||
|
||||
### enable the following line if you want to track down connection ###
|
||||
### leakages when using DriverManagerConnectionProvider ###
|
||||
@@ -25,8 +25,8 @@ log4j.rootLogger=info, stdout, chainsaw
|
||||
log4j.logger.org.springframework=error
|
||||
log4j.logger.org.springframework.batch.sample=info
|
||||
#log4j.logger.org.springframework.transaction=debug
|
||||
log4j.logger.org.springframework.jdbc.core=debug
|
||||
log4j.logger.org.springframework.orm=debug
|
||||
#log4j.logger.org.springframework.jdbc.core=debug
|
||||
#log4j.logger.org.springframework.orm=debug
|
||||
|
||||
### debug your specific package or classes with the following example
|
||||
log4j.logger.org.springframework.batch.sample.module.OrderDataProvider=debug
|
||||
|
||||
Reference in New Issue
Block a user