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

Duplicate container-info entries in kie-server-router.json file if we create containers with unique container-alias

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Minor
    • None
    • 7.8.0.GA
    • Kie-Server
    • CR1
    • Hide
      1. Configure smart router with business-central and kie-server by following steps captured in [KCS article|https://access.redhat.com/solutions/3772521]
      2.   Create first container on kie-server node with below payload: 
        PUT  http://localhost:8080/kie-server/services/rest/server/containers/itorders_1.0
      {"container-alias" : "itorders_1.0","container-id" : "itorders_1.0","release-id" : {"group-id" : "itorders","artifact-id" : "itorders","version" : "1.0.0-SNAPSHOT"}}
      1.  kie-server-router.json file will have entry for this container. Take a look at attached  kie-server-router_afterFirstContainer.json
      2. Create a second container on  kie-server node with below payload 
         PUT http://localhost:8080/kie-server/services/rest/server/containers/itorders_1.1
      {"container-alias" : "itorders_1.1","container-id" : "itorders_1.1","release-id" : {"group-id" : "itorders","artifact-id" : "itorders","version" : "1.0.01-SNAPSHOT"}}
      1. In the kie-server-router.json we can see 4 entries for 'itorders_1.0' container. And it will keep increasing everytime we create new container. Take a look at attached  kie-server-router_afterSecondContainer.json
      Show
      Configure smart router with business-central and kie-server by following steps captured in [KCS article| https://access.redhat.com/solutions/3772521 ]   Create first container on kie-server node with below payload: PUT http: //localhost:8080/kie-server/services/ rest /server/containers/itorders_1.0 { "container-alias" : "itorders_1.0" , "container-id" : "itorders_1.0" , "release-id" : { "group-id" : "itorders" , "artifact-id" : "itorders" , "version" : "1.0.0-SNAPSHOT" }}  kie-server-router.json file will have entry for this container. Take a look at attached  kie-server-router_afterFirstContainer.json Create a second container on  kie-server node with below payload PUT http: //localhost:8080/kie-server/services/ rest /server/containers/itorders_1.1 { "container-alias" : "itorders_1.1" , "container-id" : "itorders_1.1" , "release-id" : { "group-id" : "itorders" , "artifact-id" : "itorders" , "version" : "1.0.01-SNAPSHOT" }} In the kie-server-router.json we can see 4 entries for 'itorders_1.0' container. And it will keep increasing everytime we create new container. Take a look at attached  kie-server-router_afterSecondContainer.json
    • 2020 Week 40-42 (from Sep 28), 2020 Week 43-45 (from Okt 19)

    Description

      If we have configured kie-server with smart router and using unique container-alias while container creation. We can see container-info details from kie-server-router.json is duplicated everytime when we create new container. In customers environment, they have configured two kie-server's with smart router and on each kie-server they created 6 containers with unique container-alias, after this kie-server-router.json file size is 21 MB.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-3421 Smart router stops serving container when one Kie server stops

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBPM-9423 Duplicate container-info entries in kie-server-router.json file if we create containers with unique container-alias

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBPM-9566 Smart router remove container even if there are other server instances active

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Pull Request Sent

          Activity

            People

              elguardian@gmail.com Enrique González Martínez (Inactive)
              rhn-support-abhumbe Abhijit Humbe
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: