Turning off hibernate logging console output

Question

I m using hibernate 3 and want to stop it from dumping all the startup messages to the console  I tried commenting out the stdout lines in log4j properties but no luck  I ve pasted my log file below  Also I m using eclipse with the standard project structure and have a copy of log4j properties in both the root of the project folder and the bin folder       direct log messages to 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 ABSOLUTE   5p  c 1   L -  m n      direct messages to file hibernate log     log4j appender file org apache log4j FileAppender log4j appender file File hibernate log log4j appender file layout org apache log4j PatternLayout log4j appender file layout ConversionPattern  d ABSOLUTE   5p  c 1   L -  m n      set log levels - for more verbose logging change  info  to  debug       log4j rootLogger warn  stdout   log4j logger org hibernate info log4j logger org hibernate debug      log HQL query parser activity  log4j logger org hibernate hql ast AST debug      log just the SQL  log4j logger org hibernate SQL debug      log JDBC bind parameters     log4j logger org hibernate type info  log4j logger org hibernate type debug      log schema export update     log4j logger org hibernate tool hbm2ddl debug      log HQL parse trees  log4j logger org hibernate hql debug      log cache activity      log4j logger org hibernate cache debug      log transaction activity  log4j logger org hibernate transaction debug      log JDBC resource acquisition  log4j logger org hibernate jdbc debug      enable the following line if you want to track down connection         leakages when using DriverManagerConnectionProvider      log4j logger org hibernate connection DriverManagerConnectionProvider trac5

User · Answer

For disabling Hibernate select message in log  it is possible to set the property into HibernateJpaVendorAdapter      lt bean id  jpaVendorAdapter      class  org springframework orm jpa vendor HibernateJpaVendorAdapter  gt       lt property name  showSql  value  false   gt   lt  bean gt

User · Answer

Executing   java util logging Logger getLogger  org hibernate   setLevel Level OFF     before hibernate s initialization worked for me     Note  the line above will turn every logging off  Level OFF   If you want to be less strict  you can use  java util logging Logger getLogger  org hibernate   setLevel Level SEVERE     that is silent enough   Or check the java util logging Level class for more levels

User · Answer

For those who don t want elegant solutions  just a quick and dirty way to stop those messages  here is a solution that worked for me  I use Hibernate 4 3 6 and Eclipse and no answers provided above  or found on the internet  worked  neither log4j config files nor setting the logging level programatically   public static void main String   args          magical - do not touch      SuppressWarnings  unused       org jboss logging Logger logger   org jboss logging Logger getLogger  org hibernate        java util logging Logger getLogger  org hibernate   setLevel java util logging Level WARNING     or whatever level you need              I used it in a tutorial program downloaded from this site

User · Answer

I managed to stop by adding those 2 lines  log4j logger org hibernate orm deprecation error  log4j logger org hibernate error   Bellow is what my log4j properties looks like  i just leave some commented lines explaining the log level    Root logger option  Level rules TRACE  lt  DEBUG  lt  INFO  lt  WARN  lt  ERROR  lt  FATAL   FATAL  shows messages at a FATAL level only  ERROR  Shows messages classified as ERROR and FATAL  WARNING  Shows messages classified as WARNING  ERROR  and FATAL  INFO  Shows messages classified as INFO  WARNING  ERROR  and FATAL  DEBUG  Shows messages classified as DEBUG  INFO  WARNING  ERROR  and FATAL  TRACE   Shows messages classified as TRACE DEBUG  INFO  WARNING  ERROR  and FATAL  ALL   Shows messages classified as TRACE DEBUG  INFO  WARNING  ERROR  and FATAL  OFF   No log messages display   log4j rootLogger INFO  file  console  log4j logger main DEBUG log4j logger org hibernate orm deprecation error log4j logger org hibernate error                                            Direct log messages to a log file log4j appender file Threshold ALL log4j appender file file logs MyProgram log log4j appender file layout org apache log4j PatternLayout log4j appender file layout ConversionPattern  d yyyy-MM-dd HH mm ss SSS   -5p  c 1  -  m n    set file size limit log4j appender file org apache log4j RollingFileAppender log4j appender file MaxFileSize 5MB log4j appender file MaxBackupIndex 50                                                   Direct log messages to System Out log4j appender console Threshold INFO log4j appender console Target System out log4j appender console org apache log4j ConsoleAppender log4j appender console layout org apache log4j PatternLayout log4j appender console layout ConversionPattern  d HH mm ss   -5p  c 1  -  m n

User · Answer

To get rid of logger output in console try this   ch qos logback classic LoggerContext LoggerContext loggerContext    LoggerContext  org slf4j LoggerFactory LoggerFactory getILoggerFactory     loggerContext stop      These statements disabled all the console outputs from logger

User · Answer

The first thing to do is to figure out which logging framework is actually used   Many frameworks are already covered by other authors above  In case you are using Logback you can solve the problem by adding this logback xml to your classpath    lt  xml version  1 0  encoding  UTF-8   gt   lt configuration gt       lt logger name  org hibernate  level  WARN   gt   lt  configuration gt    Further information  Logback Manual-Configuration

User · Answer

Replace slf4j-jdk14-xxx jar with slf4j-log4j12-xxx jar  If you have both  delete slf4j-jdk14-xxx jar  Found this solution at https   forum hibernate org viewtopic php f 1 amp t 999623

User · Answer

For those who don t want elegant solutions  just a quick and dirty way to stop those messages  here is a solution that worked for me  I use Hibernate 4 3 6 and Eclipse and no answers provided above  or found on the internet  worked  neither log4j config files nor setting the logging level programatically   public static void main String   args          magical - do not touch      SuppressWarnings  unused       org jboss logging Logger logger   org jboss logging Logger getLogger  org hibernate        java util logging Logger getLogger  org hibernate   setLevel java util logging Level WARNING     or whatever level you need              I used it in a tutorial program downloaded from this site

User · Answer

There are several parts of hibernate logging you can control based on the logger hierarchy of the hibernate package  more on logger hierarchy here         lt  -- Log everything in hibernate -- gt       lt Logger name  org hibernate  level  info  additivity  false  gt         lt AppenderRef ref  Console    gt       lt  Logger gt        lt  -- Log SQL statements -- gt       lt Logger name  org hibernate SQL  level  debug  additivity  false  gt         lt AppenderRef ref  Console    gt         lt AppenderRef ref  File    gt       lt  Logger gt        lt  -- Log JDBC bind parameters -- gt       lt Logger name  org hibernate type descriptor sql  level  trace  additivity  false  gt         lt AppenderRef ref  Console    gt         lt AppenderRef ref  File    gt       lt  Logger gt    The above was taken from here   Additionally you could have the property show-sql true in your configuration file since that supersedes the logging framework settings  More on that here

User · Answer

There are several parts of hibernate logging you can control based on the logger hierarchy of the hibernate package  more on logger hierarchy here         lt  -- Log everything in hibernate -- gt       lt Logger name  org hibernate  level  info  additivity  false  gt         lt AppenderRef ref  Console    gt       lt  Logger gt        lt  -- Log SQL statements -- gt       lt Logger name  org hibernate SQL  level  debug  additivity  false  gt         lt AppenderRef ref  Console    gt         lt AppenderRef ref  File    gt       lt  Logger gt        lt  -- Log JDBC bind parameters -- gt       lt Logger name  org hibernate type descriptor sql  level  trace  additivity  false  gt         lt AppenderRef ref  Console    gt         lt AppenderRef ref  File    gt       lt  Logger gt    The above was taken from here   Additionally you could have the property show-sql true in your configuration file since that supersedes the logging framework settings  More on that here

User · Answer

Try to set more reasonable logging level  Setting logging level to info means that only log event at info or higher level  warn  error and fatal  are logged  that is debug logging events are ignored   log4j logger org hibernate info   or in XML version of log4j config file    lt logger name  org hibernate  gt     lt level value  info   gt    lt  logger gt    See also log4j manual

User · Answer

To get rid of logger output in console try this   ch qos logback classic LoggerContext LoggerContext loggerContext    LoggerContext  org slf4j LoggerFactory LoggerFactory getILoggerFactory     loggerContext stop      These statements disabled all the console outputs from logger

User · Answer

Important notice  the property  part of hibernate configuration  NOT part of logging framework config    hibernate show sql   controls the logging directly to STDOUT bypassing any logging framework  which you can recognize by the missing output formatting of the messages   If you use a logging framework like log4j  you should always set that property to false because it gives you no benefit at all   That circumstance irritated me quite a long time because I never really cared about it until I tried to write some benchmark regarding Hibernate

User · Answer

I managed to stop by adding those 2 lines  log4j logger org hibernate orm deprecation error  log4j logger org hibernate error   Bellow is what my log4j properties looks like  i just leave some commented lines explaining the log level    Root logger option  Level rules TRACE  lt  DEBUG  lt  INFO  lt  WARN  lt  ERROR  lt  FATAL   FATAL  shows messages at a FATAL level only  ERROR  Shows messages classified as ERROR and FATAL  WARNING  Shows messages classified as WARNING  ERROR  and FATAL  INFO  Shows messages classified as INFO  WARNING  ERROR  and FATAL  DEBUG  Shows messages classified as DEBUG  INFO  WARNING  ERROR  and FATAL  TRACE   Shows messages classified as TRACE DEBUG  INFO  WARNING  ERROR  and FATAL  ALL   Shows messages classified as TRACE DEBUG  INFO  WARNING  ERROR  and FATAL  OFF   No log messages display   log4j rootLogger INFO  file  console  log4j logger main DEBUG log4j logger org hibernate orm deprecation error log4j logger org hibernate error                                            Direct log messages to a log file log4j appender file Threshold ALL log4j appender file file logs MyProgram log log4j appender file layout org apache log4j PatternLayout log4j appender file layout ConversionPattern  d yyyy-MM-dd HH mm ss SSS   -5p  c 1  -  m n    set file size limit log4j appender file org apache log4j RollingFileAppender log4j appender file MaxFileSize 5MB log4j appender file MaxBackupIndex 50                                                   Direct log messages to System Out log4j appender console Threshold INFO log4j appender console Target System out log4j appender console org apache log4j ConsoleAppender log4j appender console layout org apache log4j PatternLayout log4j appender console layout ConversionPattern  d HH mm ss   -5p  c 1  -  m n

User · Answer

Try to set more reasonable logging level  Setting logging level to info means that only log event at info or higher level  warn  error and fatal  are logged  that is debug logging events are ignored   log4j logger org hibernate info   or in XML version of log4j config file    lt logger name  org hibernate  gt     lt level value  info   gt    lt  logger gt    See also log4j manual

User · Answer

You can disabled the many of the outputs of hibernate setting this props of hibernate  hb configuration  a false   hibernate show sql hibernate generate statistics hibernate use sql comments   But if you want to disable all console info you must to set the logger level a NONE of FATAL of class org hibernate like Juha say

User · Answer

Replace slf4j-jdk14-xxx jar with slf4j-log4j12-xxx jar  If you have both  delete slf4j-jdk14-xxx jar  Found this solution at https   forum hibernate org viewtopic php f 1 amp t 999623

User · Answer

I finally figured out  it s because the Hibernate is using slf4j log facade now  to bridge to log4j  you need to put log4j and slf4j-log4j12 jars to your lib and then the log4j properties will take control Hibernate logs   My pom xml setting looks as below        lt dependency gt           lt groupId gt log4j lt  groupId gt           lt artifactId gt log4j lt  artifactId gt           lt version gt 1 2 16 lt  version gt       lt  dependency gt        lt dependency gt           lt groupId gt org slf4j lt  groupId gt           lt artifactId gt slf4j-log4j12 lt  artifactId gt           lt version gt 1 6 4 lt  version gt       lt  dependency gt

User · Answer

Try to set more reasonable logging level  Setting logging level to info means that only log event at info or higher level  warn  error and fatal  are logged  that is debug logging events are ignored   log4j logger org hibernate info   or in XML version of log4j config file    lt logger name  org hibernate  gt     lt level value  info   gt    lt  logger gt    See also log4j manual

User · Answer

I changed the  debug  to  info  and it worked  Here is what I did   Before   log4j rootLogger debug  stdout  R   After   log4j rootLogger info  stdout  R

User · Answer

Important notice  the property  part of hibernate configuration  NOT part of logging framework config    hibernate show sql   controls the logging directly to STDOUT bypassing any logging framework  which you can recognize by the missing output formatting of the messages   If you use a logging framework like log4j  you should always set that property to false because it gives you no benefit at all   That circumstance irritated me quite a long time because I never really cared about it until I tried to write some benchmark regarding Hibernate

User · Answer

The first thing to do is to figure out which logging framework is actually used   Many frameworks are already covered by other authors above  In case you are using Logback you can solve the problem by adding this logback xml to your classpath    lt  xml version  1 0  encoding  UTF-8   gt   lt configuration gt       lt logger name  org hibernate  level  WARN   gt   lt  configuration gt    Further information  Logback Manual-Configuration

User · Answer

You can disabled the many of the outputs of hibernate setting this props of hibernate  hb configuration  a false   hibernate show sql hibernate generate statistics hibernate use sql comments   But if you want to disable all console info you must to set the logger level a NONE of FATAL of class org hibernate like Juha say

User · Answer

You can disabled the many of the outputs of hibernate setting this props of hibernate  hb configuration  a false   hibernate show sql hibernate generate statistics hibernate use sql comments   But if you want to disable all console info you must to set the logger level a NONE of FATAL of class org hibernate like Juha say

User · Answer

I finally figured out  it s because the Hibernate is using slf4j log facade now  to bridge to log4j  you need to put log4j and slf4j-log4j12 jars to your lib and then the log4j properties will take control Hibernate logs   My pom xml setting looks as below        lt dependency gt           lt groupId gt log4j lt  groupId gt           lt artifactId gt log4j lt  artifactId gt           lt version gt 1 2 16 lt  version gt       lt  dependency gt        lt dependency gt           lt groupId gt org slf4j lt  groupId gt           lt artifactId gt slf4j-log4j12 lt  artifactId gt           lt version gt 1 6 4 lt  version gt       lt  dependency gt

User · Answer

For disabling Hibernate select message in log  it is possible to set the property into HibernateJpaVendorAdapter      lt bean id  jpaVendorAdapter      class  org springframework orm jpa vendor HibernateJpaVendorAdapter  gt       lt property name  showSql  value  false   gt   lt  bean gt

User · Answer

Executing   java util logging Logger getLogger  org hibernate   setLevel Level OFF     before hibernate s initialization worked for me     Note  the line above will turn every logging off  Level OFF   If you want to be less strict  you can use  java util logging Logger getLogger  org hibernate   setLevel Level SEVERE     that is silent enough   Or check the java util logging Level class for more levels

User · Answer

You can disabled the many of the outputs of hibernate setting this props of hibernate  hb configuration  a false   hibernate show sql hibernate generate statistics hibernate use sql comments   But if you want to disable all console info you must to set the logger level a NONE of FATAL of class org hibernate like Juha say

User · Answer

I changed the  debug  to  info  and it worked  Here is what I did   Before   log4j rootLogger debug  stdout  R   After   log4j rootLogger info  stdout  R

User · Answer

Try to set more reasonable logging level  Setting logging level to info means that only log event at info or higher level  warn  error and fatal  are logged  that is debug logging events are ignored   log4j logger org hibernate info   or in XML version of log4j config file    lt logger name  org hibernate  gt     lt level value  info   gt    lt  logger gt    See also log4j manual

[java] Turning off hibernate logging console output

Examples related to java

Examples related to hibernate

Examples related to logging