Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.4.3
-
None
Description
Currently, the Enable SQL Logging button in Logging and Profiling sets net.sf.hibernate.SQL to DEBUG, which logs the SQL queries, but it does not log the parameters, so you will see entries like this:
2014-02-27 09:37:46,834 DEBUG [scheduler_Worker-8] [net.sf.hibernate.SQL] log insert into BANDANA (BANDANACONTEXT, BANDANAKEY, BANDANAVALUE, BANDANAID) values (?, ?, ?, ?)
These are not very useful without the parameters. To set the parameters, we must edit the log4j.properties manually and restart the instance. This is not possible on OnDemand due to the environment's configuration, so SQL logging with trace cannot be enabled at all.
Improve the button so that it logs parameters as well.
Attachments
Issue Links
- is related to
-
CONFSERVER-32438 Confluence Debug Logging is not going to atlassian-confluence.log.
- Closed