[ http://jira.jboss.com/jira/browse/JBPORTAL-2022?page=all ] Martin Putz updated JBPORTAL-2022: ---------------------------------- Description: If you would like to trace the SQL statements Hibernate issues to the Portal tables, you would normally set this in conf/jboss-log4j.xml: <category name="org.hibernate.type"> <priority value="DEBUG"/> </category> <category name="org.hibernate.SQL"> <priority value="DEBUG"/> </category> Due to a Hibernate bug: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2835 in combination with a specific mix of logging libraries, this does not produce any output. was: If you would like to trace the SQL statements Hibernate issues to the Portal tables, you would normally set this in conf/jboss-log4j.xml: <category name="org.hibernate.type"> <priority value="DEBUG"/> </category> <category name="org.hibernate.SQL"> <priority value="DEBUG"/> </category> Due to a Hibernate bug (//opensource.atlassian.com/projects/hibernate/browse/HHH-2835) in combination with a specific mix of logging libraries, this does not produce any output. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira