Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 821687

Summary:

Exception occurs whilst running the mortgage samples

Product:

[JBoss] JBoss Enterprise BRMS Platform 5

Reporter:

George Varsamis <gvarsami>

Component:

BRM (Guvnor)

Assignee:

manstis

Status:

CLOSED UPSTREAM

QA Contact:

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

BRMS 5.3.0.GA

CC:

mproctor, rzhang, trikkola

Target Milestone:

ER8

Flags:

manstis: needinfo+

Target Release:

BRMS 5.3.0.GA

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2025-02-10 03:19:50 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
Server Log showing the exception	none
Repository file	none

Description George Varsamis 2012-05-15 10:52:28 UTC

Description of problem:
During smoke testing, I have encountered a org.drools.RuntimeDroolsException when running the BRMS mortgage samples Test scenarios.  

Version-Release number of selected component (if applicable):
5.3.0 ER7

How reproducible:
Every single time.

Steps to Reproduce:
1. Perform smoke testing of BRMS 5.3 as described in the guide: https://docspace.corp.redhat.com/docs/DOC-89613
2. The error occurs in section "Check BRMS console and samples" of the guide
3.
  
Actual results:
Exception appears in server.log

Expected results:
There shouldn't be an exception.

Additional info:

I have attached the server.log from the smoke test run that has the exception.

I have noticed that the exception only happens once, the very first time the test is run, subsequent runs fail to produce the exception.

Comment 1 manstis 2012-05-22 13:39:49 UTC

No attachments, but will look at issue anyway...

Comment 2 manstis 2012-05-22 14:44:57 UTC

Followed instructions given, unable to re-produce with community 5.3.x branch.

Comment 3 manstis 2012-05-22 14:48:27 UTC

Please provide more information. Unable to reproduce.

Comment 4 George Varsamis 2012-05-23 12:30:20 UTC

Created attachment 586333 [details]
Server Log showing the exception

Comment 5 Ryan Zhang 2012-05-23 13:43:39 UTC

Yes, I can reproduce the issue.

Steps:
1) import the mortgage-sample-repository.xml
2) Click QA->Test Scenarios in packs->mortgages->run all scenarios

I can spot java.io.InvalidClassException: org.drools.rule.MVELDialectRuntimeData; local class incompatible: stream classdesc serialVersionUID = 8808844570772337501, local class serialVersionUID =5166066541265170937 in server.log. 
Though the mortage samples package could rebuild automatically after the error detected and run it succesfully, it would be better off  avoiding such error.

If I  rebuild all the package first before I do step2, the error won't occur.

I suspect that the mortage-sample-repository.xml in github should be updated after the mvel version updates to mvel2-2.1.0.drools16.

Comment 6 Ryan Zhang 2012-05-23 13:59:32 UTC

CC more people to get more attentions.
cc gdesmet, jliu, trikkola

Hope to pick up  fix to ER8 as more as possible.

Comment 7 manstis 2012-05-23 20:09:12 UTC

OK, exception was not causing QA not to run, but I see your point. New example repository pushed to 5.3.x branch (and attached so you can test before ER8).

Comment 8 manstis 2012-05-23 20:10:07 UTC

Created attachment 586445 [details]
Repository file

Repository file built with mvel2-2.1.0.drools16.

Comment 9 Ryan Zhang 2012-05-25 09:07:57 UTC

Please verify them on ER8.

Comment 10 George Varsamis 2012-05-25 10:24:14 UTC

I have tested the new repository file against ER8 and it works!

Comment 11 Sona Mala 2012-05-28 08:34:50 UTC

I have tested it too. I followed steps in guide and in section "Check BRMS console and samples" no exception occured in server.log.

Comment 18 Red Hat Bugzilla 2025-02-10 03:19:50 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.