Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1133556

Summary: Dashboard builder writes out a lot of statistics on INFO logging level
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Filip Elias <felias>
Component: Dashboard BuilderAssignee: Van Halbert <vhalbert>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: dlesage, vhalbert
Target Milestone: ER4Keywords: QA-Closed
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The Dashboard-builder was printing statistics on the DEBUG logging level instead of on the INFO level. A change has been applied to the hibernate.cfg.xml file so that the statistics are now logged at the correct level.
Story Points: ---
Clone Of:
: 1133575 (view as bug list) Environment:
Last Closed: 2016-02-10 08:58:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1133575, 1155511    

Description Filip Elias 2014-08-25 13:00:13 UTC
Dashboard-builder writes out a lot of statistics, for example [1]. These type of statistics should be printed on DEBUG logging level, not INFO.

[1] 14:55:03,083 INFO  [org.hibernate.engine.internal.StatisticalLoggingSessionEventListener] (ServerService Thread Pool -- 58) Session Metrics {
    86953 nanoseconds spent acquiring 1 JDBC connections;
    0 nanoseconds spent releasing 0 JDBC connections;
    0 nanoseconds spent preparing 0 JDBC statements;
    0 nanoseconds spent executing 0 JDBC statements;
    0 nanoseconds spent executing 0 JDBC batches;
    0 nanoseconds spent performing 0 L2C puts;
    0 nanoseconds spent performing 0 L2C hits;
    0 nanoseconds spent performing 0 L2C misses;
    0 nanoseconds spent executing 0 flushes (flushing a total of 0 entities and 0 collections);
    0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 entities and 0 collections)

Comment 1 Van Halbert 2014-08-25 13:02:08 UTC
This will require an override file for hibernate.cfg.xml, unless dashboard-builder can get a fix into their production branch.

Comment 2 Van Halbert 2014-08-25 13:30:24 UTC
The question is, should the log level be changed or the hibernate.cfg.xml have the following property set to false, by default:

        <!-- Enable statistics collection -->
        <property name="generate_statistics">false</property>

Comment 3 Van Halbert 2014-08-25 13:30:26 UTC
The question is, should the log level be changed or the hibernate.cfg.xml have the following property set to false, by default:

        <!-- Enable statistics collection -->
        <property name="generate_statistics">false</property>

Comment 4 Van Halbert 2014-08-25 13:30:42 UTC
The question is, should the log level be changed or the hibernate.cfg.xml have the following property set to false, by default:

        <!-- Enable statistics collection -->
        <property name="generate_statistics">false</property>

Comment 5 Van Halbert 2014-08-26 00:34:39 UTC
Add