Bug 1197626

Summary: Use proper logging for Guided Score Cards - remove stdout
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: manstis
Status: CLOSED WORKSFORME QA Contact: Zuzana Krejčová <zkrejcov>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1.0CC: kverlaen, lpetrovi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-07 16:19: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:
Attachments:
Description Flags
stdout in server.log none

Description Zuzana Krejčová 2015-03-02 09:08:06 UTC
Created attachment 997000 [details]
stdout in server.log

Description of problem:
When user creates or updates a Guided Score Card, quite a lengthy debug message is logged to stdout - see attachment. It messes up the logs quite a bit.
The information contained in that message is more suited for TRACE or at most DEBUG log level, definitely not INFO (not using stdout would help that).
It also shouldn't be done via System.out.println(..) - please use a proper logger for that.


Version-Release number of selected component (if applicable):
6.1 ER5