Bug 1265635 - Kie server controller doesn't store created container
Summary: Kie server controller doesn't store created container
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Kie-Server
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER4
: 6.2.0
Assignee: Edson Tirelli
QA Contact: Karel Suta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-23 12:00 UTC by Karel Suta
Modified: 2020-03-27 19:13 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:13:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karel Suta 2015-09-23 12:00:21 UTC
Description of problem:
When kie server controller creates container it doesn't store that container to storage. If controller try to start created container then controller cannot find created container(which wasn't stored).

It doesn't have any influence if controller is used separately as is used in memory store, but if it is integrated into BxMS then there is used VFS and this error is revealed.

Tested on WAS but this error can happen on other containers too.


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


How reproducible:
Deploy BRMS6.2.0.ER3 and kie server to WAS. Create new container in kie server controller and try to start it.
Can be simulated using KieControllerStartupIntegrationTest from kie server integration test suite, test methods testContainerCreatedAfterStartup or testContainerDisposedAfterStartup.


Steps to Reproduce:
1.
2.
3.

Actual results:
Error is thrown complaining about container not found.

Expected results:
Container is started.

Additional info:

Comment 1 Karel Suta 2015-09-23 12:07:27 UTC
Created PR with fix proposal - https://github.com/droolsjbpm/droolsjbpm-integration/pull/197

Comment 4 Karel Suta 2015-10-27 10:45:26 UTC
Verified in 6.2.0ER4, all test methods in KieControllerStartupIntegrationTest pass successfully.


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