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

Container is not started when being created

    XMLWordPrintable

Details

    • DR3
    • jBPM sprint 2

    Description

      If you create a container using controller's REST API and set status to started in this request (<status>STARTED</status>), the container will not be started. However, the state of the container on the controller will be STARTED. This can be seen using both REST API and GUI. When you try to get the container info directly from KIE Server instance, you will see that it does not exist yet. I think there are two options how to fix this:

      1. Ignore status field in container creation requests but set the container state correctly to STOPPED.
      2. Start the container automatically if STARTED state is specified in the request.

      Attachments

        Activity

          People

            swiderski.maciej Maciej Swiderski (Inactive)
            tlivora Tomáš Livora (Inactive)
            Tomáš Livora Tomáš Livora (Inactive)
            Tomáš Livora Tomáš Livora (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: