Bug 1050979 - Dashbuilder writes funny error messages to server log
Summary: Dashbuilder writes funny error messages to server log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BAM
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER1
: 6.0.1
Assignee: David Gutierrez
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-09 13:09 UTC by Radovan Synek
Modified: 2014-08-06 20:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:02:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Radovan Synek 2014-01-09 13:09:34 UTC
Steps to reproduce:
1. break the configuration of the default ExampleDS.
2. start EAP with dashbuilder
3. try to log in - white screen appears and following message (there are also other error messages explaining what's going on) is in server log:

ERROR [org.jboss.dashboard.ui.controller.ControllerServlet] (http-localhost.localdomain/127.0.0.1:8230-2) Error painting response. User might have seen something ugly in the browser if he is still there.

Although the error message is funny and I must admit I was amused, I doubt that messages like that should be presented to our customers.

Comment 1 David Gutierrez 2014-01-10 09:02:30 UTC
Message error replaced by just "Error painting response."

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

Comment 2 Ryan Zhang 2014-01-10 09:31:25 UTC
This needs to be set blocker + and PM_ack + since it has been fixed in product branch.

Comment 3 Pedro Zapata 2014-01-10 09:45:01 UTC
From the commit above it was only fixed in master, not in product branch.

Comment 4 Ryan Zhang 2014-01-10 09:47:09 UTC
Aha, right. It makes sense. 
Thanks pointing it out and cancel the requesting of blocker flag.

Comment 6 David Gutierrez 2014-01-13 17:08:06 UTC
Cherry picked from master and pushed to the 6.0.x branch:

Github commit (6.0.x): https://github.com/droolsjbpm/dashboard-builder/commit/290250fac3c68600dd6a3e65f867a47dd948200a

Comment 7 Pedro Zapata 2014-01-14 08:44:59 UTC
Ryan, these commits to 6.0.x after the creation of GA branch will NOT go into 6.0.0 but into 6.0.1, unless cherry picked from there. I believe the target milestone should not be CR1.

Comment 8 Ryan Zhang 2014-01-14 08:52:30 UTC
Oops, my mistake. 
I wasn't aware of the GA branch/tag has been created. I will remove the CR1 milestone.
Thanks for pointing it out .

(In reply to Pedro Zapata from comment #7)
> Ryan, these commits to 6.0.x after the creation of GA branch will NOT go
> into 6.0.0 but into 6.0.1, unless cherry picked from there. I believe the
> target milestone should not be CR1.

Comment 9 Lukáš Petrovický 2014-02-07 16:19:40 UTC
This no longer has a target release of 6.0.0.

Comment 10 Radovan Synek 2014-02-21 08:54:05 UTC
Verified with BPMS-6.0.1.ER1


Note You need to log in before you can comment on or make changes to this bug.