Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1910

Business-central is unable to connect to co-located controller when deployed at the same time

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.4.0.GA
    • 7.2.0.GA, 7.2.1.GA
    • Business Central
    • CR1
    • +
    • Hide

      1. Install RHPAM - Business Central and controller.war on the same EAP;
      2. Configure them by adding the following system parameters in the standalone.xml file:
      ***************************************************************
      <property name="org.kie.workbench.controller" value="ws://localhost:8080/controller/websocket/controller"/>
      <property name="org.kie.workbench.controller.user" value="controllerUser"/>
      <property name="org.kie.workbench.controller.password" value="controllerUser123!"/>
      ***************************************************************
      3. Touch/create $RHPAM/standalone/deployments/business-central.war.dodeploy and $RHPAM/standalone/deployments/controller.war.dodeploy;
      4. Start RHPAM;

      Show
      1. Install RHPAM - Business Central and controller.war on the same EAP; 2. Configure them by adding the following system parameters in the standalone.xml file: *************************************************************** <property name="org.kie.workbench.controller" value="ws://localhost:8080/controller/websocket/controller"/> <property name="org.kie.workbench.controller.user" value="controllerUser"/> <property name="org.kie.workbench.controller.password" value="controllerUser123!"/> *************************************************************** 3. Touch/create $RHPAM/standalone/deployments/business-central.war.dodeploy and $RHPAM/standalone/deployments/controller.war.dodeploy; 4. Start RHPAM;

      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.

              cnicolai@redhat.com Cristiano Nicolai (Inactive)
              rhn-support-bkramer1 Biljana Kramer
              Jan Stastny Jan Stastny
              Jan Stastny Jan Stastny
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: