Bug 1222866 - Container does not survive server restart
Summary: Container does not survive server restart
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Kie-Server
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ER3
: 6.2.0
Assignee: Edson Tirelli
QA Contact: Jakub Schwan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-19 10:24 UTC by Anton Giertli
Modified: 2020-03-27 20:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:06:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1614363 0 None None None Never

Description Anton Giertli 2015-05-19 10:24:01 UTC 
Description of problem:

If you restart BRMS then the Container deployed on a decision server will be paused - and not started. i.e. the state of the container does not seem to be persisted and it is lost after server restart. 
Version-Release number of selected component (if applicable):

BRMS 6.1.0
How reproducible:
always

Steps to Reproduce:
1. Create new decision server and deploy some container on top of it
2. start this container
3. restart BRMS
4. The container is marked as PAUSED and has to be started again

Actual results:
Container deployed on the Decision Server does not survive server restart

Expected results:
Container deployed on the Decision server does survive server restart

Additional info:
Comment 3 Edson Tirelli 2015-09-01 00:46:54 UTC 
This is by design. KieServer in version 6.1 has no configuration persistency and requires reconfiguration before a re-start. 

This is implemented and working on version 6.2.
Comment 4 Edson Tirelli 2015-09-04 19:09:59 UTC 
This is done in 6.2.
Comment 5 Jakub Schwan 2015-10-15 08:58:45 UTC 
Verified in 6.2 ER4
Note You need to log in before you can comment on or make changes to this bug.