-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
5
-
NEW
-
NEW
-
2019 Week 08-10
Attempt to run with a setup where business-central connects to the
standalone controller due to HA functionality fails after
10s due to the following:
*****************************************************************
Caused by: java.lang.RuntimeException: java.io.IOException: UT003035:
Connection timed out
at
org.kie.server.controller.websocket.common.WebSocketClientImpl.init(WebSocketClientImpl.java:108)
at
org.kie.server.controller.client.websocket.WebSocketKieServerControllerClient.<init>(WebSocketKieServerControllerClient.java:71)
at
org.kie.server.controller.client.websocket.WebSocketKieServerControllerClient.<init>(WebSocketKieServerControllerClient.java:56)
at
org.kie.server.controller.client.KieServerControllerClientFactory.newWebSocketClient(KieServerControllerClientFactory.java:114)
*****************************************************************
Attempt to increase the timeout by adding the following to WebSocketClientImpl:
*****************************************************************
this.config.getUserProperties().put("io.undertow.websocket.CONNECT_TIMEOUT",
30);
*****************************************************************
did not help.
However, If the deployments are manually triggered (first controller.war, then
business-central.war), this setup works as expected.
- causes
-
RHPAM-1920 [GSS](7.3.1) Business-central is unable to connect to co-located controller when deployed at the same time
- Closed
- relates to
-
RHPAM-1910 Business-central is unable to connect to co-located controller when deployed at the same time
- Closed