Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-5698

Starting process with new Kie server node

XMLWordPrintable

    • NEW
    • NEW
    • Hide

      Create business process, deploy to Kie server.
      Check Process definition page, process should be shown there.
      Switch to Project authoring page.
      Turn off Kie server.
      Turn on Kie server with same configuration, but placed on different IP address than the previous Kie server.
      Wait for Kie server to start.
      Open Process definition page again -> error from screenshot can be shown.

      Show
      Create business process, deploy to Kie server. Check Process definition page, process should be shown there. Switch to Project authoring page. Turn off Kie server. Turn on Kie server with same configuration, but placed on different IP address than the previous Kie server. Wait for Kie server to start. Open Process definition page again -> error from screenshot can be shown.

      If user deletes Kie server node (pod) in specific server template and creates it again with different IP address then he is unable to start a new process.

      Workbench throws exception, see screenshot.

      It seems to be caused by client load balancer containing 2 Kie servers:
      “Load balancer RoundRobinBalancerStrategy

      {availableEndpoints=[http://172.17.0.6:8080/kie-server/services/rest/server, http://172.17.0.2:8080/kie-server/services/rest/server]}

      selected url 'http://172.17.0.2:8080/kie-server/services/rest/server' ”

      It seems that Kie server client doesn't handle case when http call throws NoRouteToHostException [1].

      [1] https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-server-parent/kie-server-remote/kie-server-client/src/main/java/org/kie/server/client/impl/AbstractKieServicesClientImpl.java#L807

              swiderski.maciej Maciej Swiderski (Inactive)
              ksuta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: