-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
NEW
-
NEW
-
Undefined
-
---
-
---
-
- Configure smart router with business-central and kie-server by following steps captured in [KCS article|https://access.redhat.com/solutions/3772521]
- Create first container on kie-server node with below payload:
PUT http://localhost:8080/kie-server/services/rest/server/containers/itorders_1.0
{"container-alias" : "itorders_1.0","container-id" : "itorders_1.0","release-id" : {"group-id" : "itorders","artifact-id" : "itorders","version" : "1.0.0-SNAPSHOT"}}
- kie-server-router.json file will have entry for this container. Take a look at attached kie-server-router_afterFirstContainer.json
- Create a second container on kie-server node with below payload
PUT http://localhost:8080/kie-server/services/rest/server/containers/itorders_1.1
{"container-alias" : "itorders_1.1","container-id" : "itorders_1.1","release-id" : {"group-id" : "itorders","artifact-id" : "itorders","version" : "1.0.01-SNAPSHOT"}}
- In the kie-server-router.json we can see 4 entries for 'itorders_1.0' container. And it will keep increasing everytime we create new container. Take a look at attached kie-server-router_afterSecondContainer.json
If we have configured kie-server with smart router and using unique container-alias while container creation. We can see container-info details from kie-server-router.json is duplicated everytime when we create new container. In customers environment, they have configured two kie-server's with smart router and on each kie-server they created 6 containers with unique container-alias, after this kie-server-router.json file size is 21 MB.
- relates to
-
RHPAM-3159 Duplicate container-info entries in kie-server-router.json file if we create containers with unique container-alias
- Closed