Bug 1046037

Summary:

Whole stack present in server log if constraint editor cannot parse condition.

Product:

[Retired] JBoss BPMS Platform 6

Reporter:

Marek Baluch <mbaluch>

Component:

jBPM Designer

Assignee:

Jan <jschatte>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Marek Baluch <mbaluch>

Severity:

low

Docs Contact:

Priority:

medium

Version:

6.0.0

CC:

kverlaen, pzapataf, rrajasek

Target Milestone:

ER1

Target Release:

6.0.1

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-08-06 20:03:56 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
stack-trace	none

Description Marek Baluch 2013-12-23 10:43:07 UTC

Description of problem:
When the condition set on a sequence flow cannot be parsed by the constraint editor then the whole stack trace will be present in the server log. This potentially presents a lot of waste in the log. Please consider outputting only an error message or changing the log level.

Steps to Reproduce:
1. Create a sequence flow condition which does not have the format of 'KieFunctions.functionName(variable, params)'
2. Switch to the constraint editor.
3. Take a look into the server log

Comment 1 Marek Baluch 2013-12-23 13:55:37 UTC

Created attachment 840800 [details]
stack-trace

Comment 2 Marek Baluch 2014-01-07 12:54:38 UTC

Lowering severity as this issue represents a clear enhancement.

Comment 3 Jan 2014-01-15 16:43:46 UTC

Fixed in master: http://github.com/droolsjbpm/jbpm-designer/commit/2c46d9d79

Comment 4 Jan 2014-01-23 12:28:16 UTC

Cherry-picked into 6.0.x: http://github.com/droolsjbpm/jbpm-designer/commit/bf428084d

Comment 5 Marek Baluch 2014-02-17 12:38:06 UTC

Verified on 6.0.1.ER1.