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

Starting scanner affects different Kie Container

XMLWordPrintable

    • NEW
    • NEW
    • Hide

      Preconditions:

      • Deployed both kie-server and workbench
      • Workbench is set up as controller for kie-server
      1. Go to project authoring
      2. Create new project with GAV: dtables:reproducer:1.0
      3. Save, Build And Deploy the project
      4. Go to Deploy - Execution Servers
      5. Click on the Add Container
      6. Select the artifact with GAV: dtables:reproducer:1.0
      7. Finish the dialogue
      8. Start the newly added container
      9. Now you should have two running containers for the artifact dtables:reproducer:1.0
      10. Select the first one, named as reproducer_1.0
      11. Select the Version Configuration tab
      12. Start scanner with value 5
      13. Select the other Kie Container
        • In fact the scanner was started for this container
      Show
      Preconditions: Deployed both kie-server and workbench Workbench is set up as controller for kie-server Go to project authoring Create new project with GAV: dtables:reproducer:1.0 Save, Build And Deploy the project Go to Deploy - Execution Servers Click on the Add Container Select the artifact with GAV: dtables:reproducer:1.0 Finish the dialogue Start the newly added container Now you should have two running containers for the artifact dtables:reproducer:1.0 Select the first one, named as reproducer_1.0 Select the Version Configuration tab Start scanner with value 5 Select the other Kie Container In fact the scanner was started for this container

      User can start scanner for each Kie Container. The problem is that pressing the Start Scanner button affects a not selected Kie Container

        1. jbpm-5640.gif
          1.34 MB
          Guilherme Gomes

              karreiro_ Guilherme Gomes (Inactive)
              rh-ee-jomarko Jozef Marko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: