Bug 1318987 - Execution server controller doesn't notify Kie server when creating/deleting container
Summary: Execution server controller doesn't notify Kie server when creating/deleting ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ER2
: 6.3.0
Assignee: manstis
QA Contact: Karel Suta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 10:37 UTC by Karel Suta
Modified: 2020-03-27 20:06 UTC (History)
4 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


Attachments (Terms of Use)

Description Karel Suta 2016-03-18 10:37:40 UTC
Description of problem:
Execution server controller from business central doesn't notify Kie server if there is container started or deleted. This behaviour was simulated on REST interface of controller.

Issue seems to be caused by KieServerAdminControllerCDI, which overrides notify methods, but doesn't do anything in them.

Issue was simulated using old controller interface: http://localhost:8080/business-central/rest/controller/admin/
This issue was simulated on KieControllerIntegrationTest[1], test method testStartAndStopContainer, line 338.

[1] https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-server-parent/kie-server-tests/kie-server-integ-tests-controller/src/test/java/org/kie/server/integrationtests/controller/KieControllerIntegrationTest.java#L338


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


How reproducible:
Deploy business central and Kie server. Create Kie server. Create container in Kie server. Start container.



Steps to Reproduce:
1. Deploy business central and Kie server.
2. Create Kie server. Using for example:
PUT http://localhost:8080/business-central/rest/controller/admin/server/15ad5bfa-7532-3eea-940a-abbbbc89f1e8
3. Create container in Kie server. Using for example:
PUT http://localhost:8080/business-central/rest/controller/admin/server/15ad5bfa-7532-3eea-940a-abbbbc89f1e8/containers/kie-concurrent
4. Start container. Using for example:
POST http://localhost:8080/business-central/rest/controller/admin/server/15ad5bfa-7532-3eea-940a-abbbbc89f1e8/containers/kie-concurrent/status/started


Actual results:
Kie server doesn't contain any container.

Expected results:
Container is registered in Kie server and started.

Additional info:
This functionality worked for 6.3.0 DR2

Comment 2 Lukáš Petrovický 2016-03-18 14:32:29 UTC
Alessandro, you may want to be aware of this. This is a backwards compatibility issue - we are being told that, essentially, the old API should only be considered read-only.

Comment 4 Karel Suta 2016-03-18 15:35:58 UTC
To clarify this:
In 6.2 there is REST controller for Kie server available on URL SERVER:HOST/business-central/rest/controller/admin 
Using this controller user can control kie server instances, create and control containers.

In 6.3 this controller is deprecated, can be used just to read informations about kie servers and containers.
To start or stop containers user has to use new controller located on URL SERVER:HOST/business-central/rest/controller/management
This new controller brings additional functionality like specifying container configuration.

Comment 7 Karel Suta 2016-04-01 11:42:30 UTC
Verified in 6.3.0ER2.


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