If the entries mentioned below are not defined in the log4j.properties file, you can manually add the entries to the file in the 'Hibernate Logging' section.
Confluence uses the open source persistence framework Hibernate. This page tells you how to configure Confluence's logging to report individual SQL requests being sent to the database by Hibernate. It is useful for troubleshooting:
To enable detailed SQL logging in Confluence, you need to modify log4j.properties, located in confluence/WEB-INF/classes.
|
If you require support assistance with a database related problem, it is advisable to enable detailed SQL logging prior sending us the log files. It will assists us determining what SQL queries were running during the reported problem. |
If the entries mentioned below are not defined in the log4j.properties file, you can manually add the entries to the file in the 'Hibernate Logging' section.
Stop Confluence, then uncomment the following lines in log4j.properties:
## log hibernate prepared statements/SQL queries (equivalent to setting 'hibernate.show_sql' to 'true') log4j.logger.net.sf.hibernate.SQL=DEBUG, confluencelog log4j.additivity.net.sf.hibernate.SQL=false |
Stop Confluence, then uncomment the following lines in log4j.properties:
## log hibernate prepared statement parameter values log4j.logger.net.sf.hibernate.type=DEBUG, confluencelog log4j.additivity.net.sf.hibernate.type=false |
Stop Confluence, then edit databaseSubsystemContext.xml:
databaseSubsystemContext.xml file is at confluence/WEB-INF/classes/databaseSubsystemContext.xmldatabaseSubsystemContext.xml file is available in the confluence-2.6.0.jar file located in the <confluence-install>/WEB-INF/lib directory.Uncomment the <prop> line in the following location:
<!-- it can be useful to disable batching during debugging, as HSQLDB doesn't report the exact statement which fails in batch mode --> <prop key="hibernate.jdbc.batch_size">0</prop> |