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

Restarting the business central pod partly break off its connection to the kieserver

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.0.GA
    • 7.0.0.GA
    • None
    • ER5
    • Workaround Exists
    • Hide

      Delete the kie container and deploy a new one. This has the added side-effect of removing process instance history.

      Show
      Delete the kie container and deploy a new one. This has the added side-effect of removing process instance history.
    • Hide
      • Create a working environment:
        $ oc new-app -f rhpam70-authoring.yaml
      • Create and deploy a BPM project. Validate that a process can be started.
      • Delete the business central pod:

      $ oc delete pod -l deploymentConfig=myapp-rhpamcentr

      • Wait for the business central pod to start up again, log in and try to create a new process instance. The error dialog should appear instead.
      Show
      Create a working environment: $ oc new-app -f rhpam70-authoring.yaml Create and deploy a BPM project. Validate that a process can be started. Delete the business central pod: $ oc delete pod -l deploymentConfig=myapp-rhpamcentr Wait for the business central pod to start up again, log in and try to create a new process instance. The error dialog should appear instead.

    Description

      When a non-HA environment is properly configured with a running container, killing the business central pod appears to partly disconnect it from the KIE server. Once a new business central pod comes up, it shows the container as deployed and started on the remote server, as before. It even provides the right IP address for the KIE server and the link shows the container as running without any issues on that KIE server. However, an attempt to start a new process instance from business central fails with the following error dialog:

      Unable to complete your request. The following exception occurred: No connection to 'myapp-kieserver' server(s). Server template configuration requires container 'project_1.0.0' to be configured and started.

      Sending an independent POST request to the KIE server successfully starts the process.

      Attachments

        Issue Links

          Activity

            People

              bmozaffari-gps-jboss Babak Mozaffari
              bmozaffari-gps-jboss Babak Mozaffari
              Maciej Swiderski (Inactive)
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: