| Summary: | Impossible to run test scenarios on BRMS 5.3.0.alpha3 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Amana <ajuricic> | ||||
| Component: | BRM (Guvnor) | Assignee: | manstis | ||||
| Status: | VERIFIED --- | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | BRMS 5.3.0.GA | CC: | armenio.pinto, manstis | ||||
| Target Milestone: | --- | ||||||
| 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: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Created attachment 540841 [details]
printscreen
printscreen
This issue can also be reproduced through of mortgages project. Try to run one of the existing test scenarios in mortgages project. Requesting the 5.3.0? flag, so that it actually gets looked at for 5.3. This is out of date. Test Scenarios run OK. Please re-check with a newer version. Update status to ON_QA. Please verify them against ER6. As far as I can tell, this works. Test Scenarios are running basically without a problem. Simple TS run smoothly. In the mortgage example repository, the first test run logged an error to the server log: ERROR [RepositoryAssetService] Unable to load rule base. java.io.InvalidClassException: org.drools.rule.MVELDialectRuntimeData; local class incompatible: stream classdesc serialVersionUID = 8808844570772337501, local class serialVersionUID = 5166066541265170937 followed by: 11:40:10,357 INFO [RepositoryAssetService] ...but trying to rebuild binaries... 11:40:13,326 INFO [TransientRepository] Session closed 11:40:13,963 INFO [PackageAssembler] Following assets have been included in package build: Dummy rule, drools, MortgageModel, Underage, Are they old enough, No bankruptcies, Bankruptcy history, credit ratings, No bad credit checks, Good credit history only, no NINJAs, NINJAs, Pricing loans, Pricing low end, ApplicantDsl, CreditApproval, RegexDslRule, This though did not make anything crash, the first test just took a little longer to run. Seems to me it works well. With this in mind, setting the bug to VERIFIED. The problem you report is because the package needs to be built first. This is caused by changes to Drools Expert where the serialized model (stored in the repository) is incompatible with current class definitions. This would is not specific to test scenarios - if you attempt to execute the mortgages binary PKG (with either a KnowledgeAgent or add to a KnowledgeBuilder manually) it will fail to load. IMO, you are correct to set to VERIFIED, but I post this comment so you can understand the cause. |
When we create a new test scenario, even the simplest one, and try to run it, it fails with the error: "400 Sorry, a technical error occurred. Please contact a system administrator." Looking at the logs, the following exception is thrown: Caused by: java.lang.NoClassDefFoundError: org/drools/testframework/ScenarioRunner at org.drools.guvnor.server.RepositoryPackageService.runScenario(RepositoryPackageService.java:661) at org.drools.guvnor.server.RepositoryPackageService.runScenario(RepositoryPackageService.java:524) at org.drools.guvnor.server.RepositoryPackageService.runScenario(RepositoryPackageService.java:505) ... 55 more