Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-4790

[GSS](6.4.z) 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
    • 6.4.5
    • 6.4.2
    • Kie-Server
    • Using kie-server in managed mode (via controller) in BPM Suite 6.4.2

    • CR2
    • 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

      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:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: