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

Deactivated container becomes started after restart of Kie server

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.16.0.Final
    • 7.15.0.Final
    • KieServer
    • None
    • 1
    • NEW
    • NEW
    • Hide

      Start Kie server, create a container, deactivate it.
      Stop Kie server.
      Start Kie server again.
      Check container state (.../server/containers) -> container state is started.

      Show
      Start Kie server, create a container, deactivate it. Stop Kie server. Start Kie server again. Check container state (.../server/containers) -> container state is started.
    • 2018 Week 51-01

    Description

      When Kie server contains deactivated container and Kie server is restarted then container changes its state to started.

      This is a combination of two issues. First is that deactivated state is not stored into Kie server state. That could be solved as part of https://github.com/kiegroup/droolsjbpm-integration/pull/1677 .
      Second issue is located in ContainerManager. Containers are installed when they are in started or deactivated state (setting its state to started), but deactivated containers are not deactivated.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: