-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
To sync with Business Central (BC) and deploy services when the user deploys them through UI, KIE server initiates a connection to Controller, which is a component of BC.
In an HA deployment, Controller instances are not synchronized. And load-balancing means that a KIE server can be connected to any of the cluster instances randomly. If a user uses the UI to deploy a service on the KIE server, but the user is connected to another cluster instance, the service is never deployed. Other sync issues are also possible.
[NOTE ENG]
This requires in case of using VFS to sync / share the state.
<property name="org.uberfire.nio.git.dir" value="/opt/kie/niogit"/>
Kie Server will notify the controller about needs to be refreshed and it will pick it up from there.
In case of openshift strategy we should be fine.
[ENG NOTE]
Added a property to disable notification from kie server to controller. By default is true
org.kie.server.update.notifications.rest.enabled=true
- relates to
-
RHPAM-2965 KIE server will not always deploy services, stay in sync with Business Central when Business Central is deployed HA on-premises
- Closed
-
JBPM-10006 Status update notification should be disabled with WebSocket Controllers
- Open