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

Process instances info is accessible through different containers URLs within the same kie-server

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Minor
    • None
    • 7.38.0.Final
    • KieServer, SpringBoot
    • None
    • NEW
    • NEW
    • Hide

      While doing some tests with regards to JBPM-9178, I've come across the following issue by following below steps:

      1. Build and install locally all artifacts regarding Jira ticket JBPM-9178
      2. Build and install all kjars, modules and business service application from https://github.com/elguardian/springboot-kjar-multiversion and start business-service-application up.
      3. Execute a curl post to create an instance of evaluation_v1: 
      4. Do the same for evaluation_v2
      5. Now I run a curl get to retrieve the information regarding process Id 1, but I use container evaluation_v2 URL instead:
      6. Same goes the other way around. If I run a curl get to get process ID 2 (created through container evaluation_v2) but through container evaluation_v1 URL:
      Show
      While doing some tests with regards to JBPM-9178 , I've come across the following issue by following below steps: Build and install locally all artifacts regarding Jira ticket  JBPM-9178 Build and install all kjars, modules and business service application from  https://github.com/elguardian/springboot-kjar-multiversion  and start business-service-application up. Execute a curl post to create an instance of  evaluation_v1 :  http://localhost:8090/rest/server/containers/evaluation_v1/processes/Evaluation.Evaluation/instances id 1 (for example) is successfully returned Do the same for  evaluation_v2 http://localhost:8090/rest/server/containers/evaluation_v2/processes/Evaluation.Evaluation/instances Eg. Id 2 is returned. Now I run a curl get to retrieve the information regarding process Id 1, but I use container  evaluation_v2  URL instead: http://localhost:8090/rest/server/containers/evaluation_v2/processes/instances/1 Info regarding process id 1 is fetched successfully. Same goes the other way around. If I run a curl get to get process ID 2 (created through container evaluation_v2) but through container  evaluation_v1  URL: http://localhost:8090/rest/server/containers/evaluation_v1/processes/instances/2 Info regarding process id 2 is fetched successfully.
    • 2020 Week 37-39 (from Sep 7), 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25)

    Description

      While doing some tests with regards to JBPM-9178, I've come across the following:

      When having more multiple kjars deployed on the same kie server but in different containers, you are able to retrieve a specific process instance info created in a particular container by calling the URL of a different container where the process instance was not created.

      All info related to a process/tasks etc created in a particular container, should only be accessible by calling the right URL container (the one where these were created initially)

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JBPM-9178 Immutable SpringBoot Deployment

          • 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. RHPAM-3311 Using container alias in rest api call is not working as expected

          • 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.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-3625 Able to execute process admin REST API's without valid containerID

          • 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.
          • Closed

          Activity

            People

              antferna Antonio Fernandez Alhambra (Inactive)
              antferna Antonio Fernandez Alhambra (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: