Bug 724230 (BRMS-174) - Unusable error message during test scnario execution: Exception executing predicate org.drools.base.mvel.MVELPredicateExpression@739c6e
Summary: Unusable error message during test scnario execution: Exception executing pre...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-174
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: 5.0.1
Assignee: Mark Proctor
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-07 14:53 UTC by nwallace
Modified: 2009-10-05 04:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-01 12:26:00 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-174 0 Minor Closed Unusable error message during test scnario execution: Exception executing predicate org.drools.base.mvel.MVELPredicateEx... 2014-02-28 14:59:42 UTC

Description nwallace 2009-07-07 14:53:34 UTC
Date of First Response: 2009-09-10 02:10:57
securitylevel_name: Public

With Guvnor 5.0.0.CR1 it seems that I have produced an error in a decision table which only appears during test scenario execution.
However the error message given in the browser (and on the console) is not very helpful:
{code}
2009-04-17 15:31:28,691 INFO  [STDOUT] ERROR 17-04 15:31:28,690 (ServiceImplementation.java:runScenario:1875)    org.drools.RuntimeDroolsException: Exception executing predicate org.drools.base.mvel.MVELPredicateExpression
{code}

As far as I know it's possible to extract the actual expression from MVELPredicateExpression and it would be nice if this gets printed so that users have a chance of fixing the problem. ;-)

Comment 1 nwallace 2009-07-07 14:55:02 UTC
Link: Added: This issue is related to JBRULES-2066


Comment 2 nwallace 2009-09-01 12:26:00 UTC
Fix in place.

Comment 3 David Le Sage 2009-09-10 06:10:57 UTC
For documenting this in the Release Notes, can you please confirm the following and fill in the missing information. Dot point explanations are fine:

The CAUSE (what was actually broken)
 * 

CONSEQUENCES of the bug (how it impacts users.)
 * During the execution of test scenarios, the following error message could appear under certain circumstances:
                2009-04-17 15:31:28,691 INFO [STDOUT] ERROR 17-04
                15:31:28,690 (ServiceImplementation.java:runScenario:1875)
                org.drools.RuntimeDroolsException: Exception executing
                predicate
                org.drools.base.mvel.MVELPredicateExpression.
 * This error message was not considered helpful to debugging as it lacked information.

The FIX (what was changed to eliminate this bug) and 
 * toStrings() has been added to the MVEL

RESULTS of the fix (what now happens for users.)
 * The expression text is now displayed as part of the error message. 
 *  This is in order to provide the troubleshooter with more helpful information.

Comment 4 David Le Sage 2009-09-23 05:51:05 UTC
We are still awaiting the outstanding information for the Release Notes on this one. Please provide it as soon as possible. Thanks.

Comment 5 Dana Mison 2009-10-05 03:17:09 UTC
added to the 5.0.CP01 release notes as resolved:

JBRULES-2066
Some of the error messages returned by MVEL rules during the execution of test scenarios where not very usable. The toStrings() method has been added to the MVEL so the error messages can include the expression text.



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