Hibernate not showing sql statement even with sql_show=true

Question

I am not sure why it doesn't show sql statement. I have it working before (on older spring, I am using 3 this time)

In ApplicationContext I have :

<bean id="mySessionFactory" class="org.springframework.orm.hibernate3.annotation.AnnotationSessionFactoryBean">
    <property name="dataSource" ref="myDataSource"/>
    <property name="hibernateProperties">
        <props>
            <prop key="hibernate.dialect">org.hibernate.dialect.OracleDialect</prop>
            <prop key="hibernate.show_sql">true</prop>
        </props>
    </property>
    <property name="packagesToScan">
        <list>
            <value>my.model.*</value>
        </list>
    </property>
</bean>

In log4j:

# Standrd System.out appender
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.Threshold=DEBUG
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p %c{1}:%L - %m%n

# package override setting
log4j.logger.org.hibernate.SQL=DEBUG, stdout
log4j.additivity.org.hibernate.SQL=false
log4j.logger.org.displaytag=INFO

log4j.rootLogger=DEBUG, stdout

Everything else seems fine, but it just doesn't show me the sql.

Did I miss anything?

(Or is it possible to print from SessionFactory from org.hibernate.cfg.Environment.getProperties()? It is not showing the show_sql, probably not even injected properly?)

Please help Thanks in advance!

I have added log4j.logger.org.hibernate.type=TRACE but still no luck. — Roy Chan
– Roy Chan, Commented Aug 16, 2011 at 17:04
By the way, I am using JPA (annotation) for mapping and I use a generic DAO to create my model's DAO (using spring to inject the model into the a class which extends HibernateDaoSupport) — Roy Chan
– Roy Chan, Commented Aug 16, 2011 at 17:07

dr jerry · Accepted Answer · 2011-08-16 14:04:51Z

11

make sure DEBUG is good, at one point hibernate logging changed from DEBUG to TRACE. Also make sure there is no threshold in your log4j.config. if you want also your arguments to be displayed include org.hibernate.type. You may also need to set org.hibernate.jdbc=TRACE or try org.hibernate=TRACE analyse your needs and change back to proper levels per package.

edited Aug 16, 2011 at 14:04

answered Aug 16, 2011 at 11:09

dr jerry

10.1k25 gold badges86 silver badges127 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Ryan Stewart Over a year ago

The hibernate.show_sql property isn't governed by logging. It writes directly to stdout.

dr jerry Over a year ago

It did do that, but it has changed in the past. On my console I get:

[8/16/11 15:20:52:058 CEST] 00000038 SystemOut     O 15:20:52.056 DEBUG [WebContainer : 6] org.hibernate.jdbc.util.SQLStatementLogger.logStatement:111 - select obfuscate0_.OUR_ID as OUR1_77_, obfuscate0_.USR_ID as USR2_77_, obfuscate0_.OFFICE as LVE3_77_, obfuscate0_.IDG_ID as IDGT4_77_, obfuscate0_.USRID_L

Roy Chan Over a year ago

it worked. and it ended up to me my mistake, entity not loaded properly

Ajitesh Over a year ago

Adding logging.level.org.hibernate=TRACE in the application.properties file worked for me.

Ryan Stewart · Accepted Answer · 2011-08-16 14:08:53Z

4

You have hibernate.show_sql configured correctly. Where are you looking for the output? In any case, it's better to just forget about show_sql and use Hibernate's logging instead. It's much more flexible. Remove the "hibernate.show_sql" property entirely, and in your logging config use

log4j.logger.org.hibernate.SQL=TRACE
log4j.logger.org.hibernate.type=TRACE

Note that there's no reason to mess with the additivity since everything is writing to the same appender, so this line doesn't do anything and should be removed:

log4j.additivity.org.hibernate.SQL=false

answered Aug 16, 2011 at 14:08

Ryan Stewart

130k22 gold badges183 silver badges201 bronze badges

2 Comments

Roy Chan Over a year ago

added a System.out.println on the class for debug purpose. so I think I am checking the right log. =(

Roy Chan Over a year ago

it worked. and it ended up to me my mistake, entity not loaded properly

Lukas Würzburger · Accepted Answer · 2019-05-16 17:03:49Z

1

In my case, I managed to correct this by adding a argument on JBoss launch configuration:

Double click on "Red Hat JBoss EAP xxx".
Click in "Open launch ocnfiguration" (tab "General Information").
Add -Dorg.jboss.as.logging.per-deployment=false on the end of "VM arguments" field.

Worked for me.

edited May 16, 2019 at 17:03

Lukas Würzburger

6,7437 gold badges46 silver badges77 bronze badges

answered May 16, 2019 at 14:55

Renato Camargos

811 silver badge2 bronze badges

Collectives™ on Stack Overflow

Hibernate not showing sql statement even with sql_show=true

3 Answers 3

4 Comments

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

4 Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related