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

KieScanner is not started correctly in kie-server if started via Managed Controller Rest Api in BPM Suite 6.4.x

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.0.GA
    • 6.x.x
    • Kie-Server

    • Using kie-server in managed mode (via controller) in BPM Suite 6.4.2

    • ER2
    • Workaround Exists
    • Hide

      Restart kie-server node, so changes applied from controller will be reflected.

      Show
      Restart kie-server node, so changes applied from controller will be reflected.
    • Hide

      1. create a xml file as follows - Payload (updatescanner.xml):

      <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rule-config>
        <pollInterval>15</pollInterval>
        <scannerStatus>STARTED</scannerStatus>
</rule-config>

      2. execute curl command:

      curl -X POST -H 'Content-type: application/xml' -H 'X-KIE-ContentType: XML' -u 'user:pass' -d @updatescanner.xml 'http://localhost:8080/business-central/rest/controller/management/servers/{kieserver-id}/containers/{container_id}/config/RULE'

      3. if you hit container url via controller, you will see that scanner will be enabled. However, if you hit it directlty through kie-server, kiescanner will not disabled.

      It will still require a kie-server restart to get changes reflected for kie-server node, or enable it directly in kie-server. Looking for the endpoint.

      Show
      1. create a xml file as follows - Payload (updatescanner.xml): <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <rule-config> <pollInterval>15</pollInterval> <scannerStatus>STARTED</scannerStatus> </rule-config> 2. execute curl command: curl -X POST -H 'Content-type: application/xml' -H 'X-KIE-ContentType: XML' -u 'user:pass' -d @updatescanner.xml 'http://localhost:8080/business-central/rest/controller/management/servers/{kieserver-id}/containers/{container_id}/config/RULE' 3. if you hit container url via controller, you will see that scanner will be enabled. However, if you hit it directlty through kie-server, kiescanner will not disabled. It will still require a kie-server restart to get changes reflected for kie-server node, or enable it directly in kie-server. Looking for the endpoint.
    • 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50

      By starting kiescanner through Managed Controller Rest API, the change is not reflected to kie-server node wihtout a kie-server restart. Then kiescanner for a container is not started properly, even though business-central shows it is started. See steps to reproduce.

              lleveric Lance Leverich (Inactive)
              rhn-support-ajuricic Amana Juricic
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: