+++ This bug was initially created as a clone of Bug #1133575 +++

+++ This bug was initially created as a clone of Bug #1133556 +++

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)

— Additional comment from Van Halbert on 2014-08-25 08:02:08 CDT —

This will require an override file for hibernate.cfg.xml, unless dashboard-builder can get a fix into their production branch.

— Additional comment from Van Halbert on 2014-08-25 08:30:24 CDT —

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>

— Additional comment from Van Halbert on 2014-08-25 08:30:26 CDT —

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>

— Additional comment from Van Halbert on 2014-08-25 08:30:42 CDT —

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>

— Additional comment from JBoss Product and Program Management on 2014-08-25 09:40:06 EDT —

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

— Additional comment from David Gutierrez on 2014-10-09 12:37:42 EDT —

Indeed. The solution is to set the property "generate_statistics" to false.

Github commit (master): https://github.com/droolsjbpm/dashboard-builder/commit/f83ee1e3f5cb04814b16a7a033c4efe49af5d0cd

— Additional comment from David Gutierrez on 2014-10-14 08:25:35 EDT —

Cherry picked into 6.0.x

https://github.com/droolsjbpm/dashboard-builder/commit/ad42a6436f510e353b1efbec4f5d4d12d821b7d5

— Additional comment from Ryan Zhang on 2014-10-15 05:00:55 EDT —

Dashbuilder brew build for 6.0.x branch is availabe at https://brewweb.devel.redhat.com/buildinfo?buildID=391356

I think there is no need to package this for 6.0.3 rollup #1. Since this is requested only for DV release based on the disucssion in PM maillist.

Only backport and build is required.

— Additional comment from Ryan Zhang on 2014-10-15 05:01:36 EDT —

The dashbuilder version including this fixes is 6.0.3-redhat-7.
Brew link: https://brewweb.devel.redhat.com/buildinfo?buildID=391356

— Additional comment from Ryan Zhang on 2014-10-20 04:34:16 EDT —

Packed into rollup patch now which is in http://dev138.mw.lab.eng.bos.redhat.com/patches/BPMS_6.0.3_1_2014/.