Stop ColdFusion 10 from logging to hibernatesql.log

Size: px

Start display at page:

Download "Stop ColdFusion 10 from logging to hibernatesql.log"

Harold Harmon
6 years ago
Views:

1 Stop ColdFusion 10 from logging to hibernatesql.log boyzoid Does anyone know how to stop CF from logging SQL to hibernatesql.log? We have logging turned off at the application level, but the hibernatesql.log file still gets written to. Thoughts? Jun 20, 1:55 PM boyzoid Also...how can I stop it from logging to coldfusion_ouit.log Scott Stroz No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced On Thu, Jun 20, 2013 at 1:56 PM, Scott Stroz - CF_CAB_General_Discussion Scott Stroz wrote: Does anyone know how to stop CF from logging SQL to hibernatesql.log? We have logging turned off at the application level, but the hibernatesql.log file still gets written to. Thoughts? Jun 20, 2:09 PM boyzoid I should have mentioned, hibernatesql.log and coldfusion_out.log are getting HUGE...quickly...and are not getting recycled according to the log file settings. Scott Stroz No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced On Thu, Jun 20, 2013 at 1:56 PM, Scott Stroz - CF_CAB_General_Discussion Scott Stroz wrote: Does anyone know how to stop CF from logging SQL to hibernatesql.log? We have logging turned off at the application level, but the hibernatesql.log file still gets written to. Thoughts? Jun 20, 2:18 PM cfjedimaster I ll add that I ve seen this myself as well on another server. The log got _huge_ quickly. I just assumed I had done something wrong (still a chance of that ;). On Thu, Jun 20, 2013 at 1:19 PM, Scott Stroz - CF_CAB_General_Discussion Scott Stroz wrote:

2 I should have mentioned, hibernatesql.log and coldfusion_out.log are getting HUGE...quickly...and are not getting recycled according to the log file settings. Scott Stroz No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced On Thu, Jun 20, 2013 at 1:56 PM, Scott Stroz - CF_CAB_General_Discussion <prforums@adobe.com<mailto:prforums@adobe.com> <mailto:prforums@adobe.com<mailto:prforums@adobe.com>>> wrote: Scott Stroz wrote: Does anyone know how to stop CF from logging SQL to hibernatesql.log? We have logging turned off at the application level, but the hibernatesql.log file still gets written to. Thoughts? Jun 20, 2:23 PM scrittler here i thought it was just me or a quirk of the server i was working on. The log not rolling over was a bigger concern - it s 1.3GB as of right now (yikes). Relevant parts of the log4j.properties file are being ignored: <code> ### Set Hibernate log log4j.logger.org.hibernate=error, HIBERNATECONSOLE ### log just the SQL log4j.logger.org.hibernate.sql=debug, HIBERNATECONSOLE log4j.additivity.org.hibernate.sql=false ### Also log the parameter binding to the prepared statements. #log4j.logger.org.hibernate.type=debug ### log schema export/update ### #log4j.logger.org.hibernate.tool.hbm2ddl=error ### log cache activity ### log4j.logger.org.hibernate.cache=error, HIBERNATECONSOLE # HibernateConsole is set to be a ColsoleAppender for Hibernate message using a PatternLayout. log4j.appender.hibernateconsole.file=c:/coldfusion10/cfusion/logs/hibernatesql.log log4j.appender.hibernateconsole.append=true log4j.appender.hibernateconsole.maxfilesize=500kb log4j.appender.hibernateconsole.maxbackupindex=3 log4j.appender.hibernateconsole.layout=org.apache.log4j.patternlayout log4j.appender.hibernateconsole.layout.conversionpattern=%d{mm/dd HH:mm:ss} [%t] HIBERNATE %-5p - %m%n%n </code> Jun 20, 2:27 PM sam.farmer As CF10 adds Hiberbate SQL to the cf debugging information, a "thinking-out-loud" idea is to check the Debugging Settings in CF Admin especially the Database Activity one. Maybe changing those fixes this? Jun 20, 4:43 PM

3 phill.nacelli What log level setting do you have on your log4j file? If you see DEBUG you may want to change to ERROR so it doesn t log everything: ### Hibernate Log Settings ### Set Hibernate log log4j.logger.org.hibernate=error, HIBERNATECONSOLE ### log just the SQL log4j.logger.org.hibernate.sql=error, HIBERNATECONSOLE log4j.additivity.org.hibernate.sql=false ### Also log the parameter binding to the prepared statements. #log4j.logger.org.hibernate.type=debug I just checked my log4j file and the append settings are commented out, can you guys confirm that s the default, maybe that s what s causing the large files: # HibernateConsole is set to be a ColsoleAppender for Hibernate message using a PatternLayout. log4j.appender.hibernateconsole.file=c:/coldfusion10/cfusion/logs/hibernatesql.log log4j.appender.hibernateconsole.append=true log4j.appender.hibernateconsole.layout=org.apache.log4j.patternlayout log4j.appender.hibernateconsole.layout.conversionpattern=%d{mm/dd HH:mm:ss} [%t] HIBERNATE %-5p - %m%n%n Phill Nacelli Senior Software Architect, Solutions Lead AboutWeb, LLC Adobe Community Professional ColdFusion User Group Manager Jun 20, 5:19 PM sam.farmer Phill Nacelli said: I just checked my log4j file and the append settings are commented out, can you guys confirm that s the default, maybe that s what s causing the large files: # HibernateConsole is set to be a ColsoleAppender for Hibernate message using a PatternLayout. log4j.appender.hibernateconsole.file=c:/coldfusion10/cfusion/logs/hibernatesql.log log4j.appender.hibernateconsole.append=true log4j.appender.hibernateconsole.layout=org.apache.log4j.patternlayout log4j.appender.hibernateconsole.layout.conversionpattern=%d{mm/dd HH:mm:ss} [%t] HIBERNATE %-5p - %m%n%n I checked an install on Windows and Mac and both have the same settings you highlighted here Phil. I know I did not change them so it looks like that is the configuration CF is shipping with. Un-believ-able. For me ORM was the jewel of CF9 which inspired me to write three ORM based presentations (that I have given 10+ times). In CF10 its been a bit of a disaster; ORM Search does not work in a cluster yet is only available in Enterprise, problems with cache conflicts on start up a year after release, and now the logs are screwed up. I feel you ve taken the jewel and made it a piece of coal. Jun 20, 10:08 PM cfjedimaster So since this big log thing has hit a bunch of us, can someone please write up a blog post to warn folks? Has anyone tested uncommenting what Phil found and see if it works?

On Thu, Jun 20, 2013 at 9:09 PM, Sam Farmer - CF_CAB_General_Discussion Sam Farmer wrote: Phill Nacelli said: I just checked my log4j file and the append settings are commented out, can you guys

4 On Thu, Jun 20, 2013 at 9:09 PM, Sam Farmer - CF_CAB_General_Discussion Sam Farmer wrote: Phill Nacelli said: I just checked my log4j file and the append settings are commented out, can you guys confirm that s the default, maybe that s what s causing the large files: # HibernateConsole is set to be a ColsoleAppender for Hibernate message using a PatternLayout. log4j.appender.hibernateconsole.file=c:/coldfusion10/cfusion/logs/hibernatesql.log log4j.appender.hibernateconsole.append=true log4j.appender.hibernateconsole.layout=org.apache.log4j.patternlayout log4j.appender.hibernateconsole.layout.conversionpattern=%d{mm/dd HH:mm:ss} [%t] HIBERNATE %-5p - %m%n%n I checked an install on Windows and Mac and both have the same settings you highlighted here Phil. I know I did not change them so it looks like that is the configuration CF is shipping with. Un-believ-able. For me ORM was the jewel of CF9 which inspired me to write three ORM based presentations (that I have given 10+ times). In CF10 its been a bit of a disaster; ORM Search does not work in a cluster yet is only available in Enterprise, problems with cache conflicts on start up a year after release, and now the logs are screwed up. I feel you ve taken the jewel and made it a piece of coal. Jun 20, 10:17 PM phill.nacelli So I changed the MaxFileSize property to 10KB and the log level to TRACE (log everything) and it s still not working, look at the size of the log file and there aren t any cycled backup files (.1,.2, etc):

Turns out in order to use the MaxFileSize and MaxBackupIndex settings you have to change the org.apache.log4j.fileappender libray to org.apache.log4j.rollingfileappender then it will work: log4j.

png Phill Nacelli Senior Software Architect, Solutions Lead AboutWeb, LLC Adobe Community Professional ColdFusion User Group Manager Jun 21, 2013 @ 10:25 AM phill.

5 Turns out in order to use the MaxFileSize and MaxBackupIndex settings you have to change the org.apache.log4j.fileappender libray to org.apache.log4j.rollingfileappender then it will work: log4j.png hibernatesql_log.png log4j_rolling.png hibernatesql_log_rolling.png Phill Nacelli Senior Software Architect, Solutions Lead AboutWeb, LLC Adobe Community Professional ColdFusion User Group Manager Jun 21, 10:25 AM phill.nacelli So turns out that most folks probably think that the "Max file size" value on the logging settings will also affect the hibernate log, but it s controlled by the log4j.properties files. Now I m curious if the other logs are using another instance of log4j or another logging mechanism altogether. Anyone from CF Team, can you clarify how logging works? Thanks,

CFAdmin_LogSettings.png Phill Nacelli Senior Software Architect, Solutions Lead AboutWeb, LLC Adobe Community Professional ColdFusion User Group Manager Jun 21, 2013 @ 11:21 AM phill.

6 CFAdmin_LogSettings.png Phill Nacelli Senior Software Architect, Solutions Lead AboutWeb, LLC Adobe Community Professional ColdFusion User Group Manager Jun 21, 11:21 AM phill.nacelli Here s another inconsistency that my colleague David Epler noticed: in the CF10 docs (which is the exact same as the for this page) under Logging you can see that supposedly the default hibernate loggging behavior is to the console: org.apache.log4j.consoleappender But if you look at a CF10 Base install the logging behavior is set to org.apache.log4j.fileappender which is creating the large log files. So the question is, is the log4j.properties file correct or someone accidently checked in the wrong version while doing some debugging? Phill Nacelli Senior Software Architect, Solutions Lead AboutWeb, LLC Adobe Community Professional ColdFusion User Group Manager Jun 21, 11:41 AM boyzoid Finally got around to looking at this again and was able to stop hibernate from logging by commenting out EVERY line related to hibernate in the block starting around line 24 Scott Stroz

7 No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced On Fri, Jun 21, 2013 at 11:48 AM, Phill Nacelli - CF_CAB_General_Discussion Phill Nacelli wrote: Here s another inconsistency that my colleague David Epler noticed: in the CF10 docs (which is the exact same as the for this page) under Logging you can see that supposedly the default hibernate loggging behavior is to the console: org.apache.log4j.consoleappender 9E5E-26B66ACA9E81.html But if you look at a CF10 Base install the logging behavior is set to org.apache.log4j.fileappender which is creating the large log files. So the question is, is the log4j.properties file correct or someone accidently checked in the wrong version while doing some debugging? Jun 21, 12:22 PM rukumar@adobe.com Check out this blog entry which gives all the details about Hibernate logging. Rupesh Adobe ColdFusion Team Jun 26, 12:34 PM cfjedimaster Rupesh, that isn t necessarily the issue. The issue is that it seems (based on what Phil said) that the log settings in CF10 may be bad now. Or am I misunderstanding? On Wed, Jun 26, 2013 at 11:48 AM, Rupesh Kumar - CF_CAB_General_Discussion Rupesh Kumar wrote: Check out this blog entry which gives all the details about Hibernate logging. Jun 26, 1:06 PM phill.nacelli Rupesh, Currently the org.apache.log4j.fileappender setting will keep logging (ERROR level, but it can be significant on a development environment), as it stands it seems there s no way that the file size will be limited under this configuration. hence the suggestion to remove the comments on these lines: and change the default log file appender library line below to org.apache.log4j.rollingfileappender:

8 The documentation only tells folks how to make these changes, but the default setting as it stands now may not be the most optimal. Can you please verify and confirm that the current installation s default log4j.properties settings are correct? Thanks, Phill Nacelli Senior Software Architect, Solutions Lead AboutWeb, LLC Adobe Community Professional ColdFusion User Group Manager Jun 26, 3:00 PM rukumar@adobe.com Thanks Phil for explaining it in detail. I should have read the complete thread :) I am not sure how it was left as FileAppender. It should definitely be RollingFileAppender. Is there any E/R logged for this? From: Phill Nacelli - CF_CAB_General_Discussion [mailto:prforums@adobe.com] Sent: Thursday, June 27, :31 AM To: Rupesh Kumar Subject: RE: Stop ColdFusion 10 from logging to hibernatesql.log - CF_CAB_General_Discussion - ColdFusion_CAB_Forums Phill Nacelli wrote: Rupesh, Currently the org.apache.log4j.fileappender setting will keep logging (ERROR level, but it can be significant on a development environment), as it stands it seems there s no way that the file size will be limited under this configuration. hence the suggestion to remove the comments on these lines: and change the default log file appender library line below to org.apache.log4j.rollingfileappender: The documentation only tells folks how to make these changes, but the default setting as it stands now may not be the most optimal. Can you please verify and confirm that the current installation s default log4j.properties settings are correct? Thanks, Rupesh Adobe ColdFusion Team Jun 28, 1:59 PM atuttle One thing I ll note here is that you should only change it during the update if it is **still set to the default value**. I d be pretty pissed if I lost my config customizations by installing an update. (Though granted it s _only_ logging settings... but still...) Adam On Fri, Jun 28, 2013 at 1:59 PM, Rupesh Kumar - CF_CAB_General_Discussion Rupesh Kumar wrote: Thanks Phil for explaining it in detail. I should have read the complete thread :) I am not sure how it was left as FileAppender. It should definitely be RollingFileAppender.

9 Is there any E/R logged for this? From: Phill Nacelli - CF_CAB_General_Discussion [mailto:prforums@adobe.com<mailto:prforums@adobe.com>] Sent: Thursday, June 27, :31 AM To: Rupesh Kumar Subject: RE: Stop ColdFusion 10 from logging to hibernatesql.log - CF_CAB_General_Discussion - ColdFusion_CAB_Forums Phill Nacelli wrote: Rupesh, Currently the org.apache.log4j.fileappender setting will keep logging (ERROR level, but it can be significant on a development environment), as it stands it seems there s no way that the file size will be limited under this configuration. hence the suggestion to remove the comments on these lines: and change the default log file appender library line below to org.apache.log4j.rollingfileappender: The documentation only tells folks how to make these changes, but the default setting as it stands now may not be the most optimal. Can you please verify and confirm that the current installation s default log4j.properties settings are correct? Thanks, Jun 30, 3:44 PM rukumar@adobe.com That s right. We will have to see if we can update it for update. We will definitely change it for Splendor. From: Adam Tuttle - CF_CAB_General_Discussion [mailto:prforums@adobe.com] Sent: Monday, July 01, :16 AM To: Rupesh Kumar Subject: RE: Stop ColdFusion 10 from logging to hibernatesql.log - CF_CAB_General_Discussion - ColdFusion_CAB_Forums Adam Tuttle wrote: One thing I ll note here is that you should only change it during the update if it is **still set to the default value**. I d be pretty pissed if I lost my config customizations by installing an update. (Though granted it s _only_ logging settings... but still...) Adam On Fri, Jun 28, 2013 at 1:59 PM, Rupesh Kumar - CF_CAB_General_Discussion <prforums@adobe.com<mailto:prforums@adobe.com<mailto:prforums@adobe.com%3cmailto:prforums@adobe.com>>> wrote: Rupesh Kumar wrote: Thanks Phil for explaining it in detail. I should have read the complete thread :) I am not sure how it was left as FileAppender. It should definitely be RollingFileAppender. Is there any E/R logged for this? From: Phill Nacelli - CF_CAB_General_Discussion [mailto:prforums@adobe.com<mailto:prforums@adobe.com> <mailto:prforums@adobe.com%3cmailto:prforums@adobe.com%3e>] Sent: Thursday, June 27, :31 AM To: Rupesh Kumar Subject: RE: Stop ColdFusion 10 from logging to hibernatesql.log - CF_CAB_General_Discussion - ColdFusion_CAB_Forums

10 Phill Nacelli wrote: Rupesh, Currently the org.apache.log4j.fileappender setting will keep logging (ERROR level, but it can be significant on a development environment), as it stands it seems there s no way that the file size will be limited under this configuration. hence the suggestion to remove the comments on these lines: and change the default log file appender library line below to org.apache.log4j.rollingfileappender: The documentation only tells folks how to make these changes, but the default setting as it stands now may not be the most optimal. Can you please verify and confirm that the current installation s default log4j.properties settings are correct? Thanks, Rupesh Adobe ColdFusion Team Jul 1, 8:07 AM sam.farmer Yes you should check. Still I d be pretty surprised if anyone had changed the _three_ settings to match what CF ships with and _wants_ it to run that way in production. Current configuration is setting up the server to run out of room. Jul 1, 9:34 AM

The name of our class will be Yo. Type that in where it says Class Name. Don t hit the OK button yet.

The name of our class will be Yo. Type that in where it says Class Name. Don t hit the OK button yet. Mr G s Java Jive #2: Yo! Our First Program With this handout you ll write your first program, which we ll call Yo. Programs, Classes, and Objects, Oh My! People regularly refer to Java as a language that