Bug 1304968 - Not possible to use Stateless session in Test Scenarios
Not possible to use Stateless session in Test Scenarios
Status: NEW
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: Business Central (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: ---
: ---
Assigned To: Toni Rikkola
Jiri Locker
Depends On:
  Show dependency treegraph
Reported: 2016-02-05 02:16 EST by Anton Giertli
Modified: 2016-07-31 21:11 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2152821 None None None 2016-02-05 02:26 EST

  None (edit)
Description Anton Giertli 2016-02-05 02:16:12 EST
Description of problem:
I have inspected the internal classes responsible for actual execution of Test Scenarios and noticed that whenever it is necessary to create a KieSession only Stateful will be created. So supplying a Stateless KieSession is simply not allowed - it will fail with this error message:

Test scenario runner could not find a stateful knowledge session with the name 'defaultSession'.

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

BRMS 6.2.0
BPM Suite 6.2.0

How reproducible:

Steps to Reproduce:
1. Define Stateless session in business-central or directly in kmodule.xml
2. Configure Test Scenario with it
3. Run it

Actual results:
Test Scenarios can be configured only with Stateful session.

Expected results:
Test Scenarios can be configured with both, Stateful and Stateless sessions

Additional info:
Only Stateful is created
Comment 2 Toni Rikkola 2016-02-05 10:04:00 EST
This is because the test scenarios can only be used with stateful sessions. Workaround is to make a stateful session for testing, but this is not ideal because then your not testing with the session that is used in production.

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