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

[GSS] (7.8.x) Business Central - Blank process diagram for processes with long running tasks

    XMLWordPrintable

Details

    • False
    • False
    • NEW
    • NEW
    • Undefined
    • Hide

      1. Import the attached project "fail-over-non-async.zip" into BC and deploy to kie-server
      2. Start a process instance for the process definition "fail-over-non-async.long-wait"
      3. Open the process instance diagram for the process instance that was started in step 2.
      4. The diagram will be "blank" as shown in the attachment "Blank_Process_Instance_Diagram.png" (while the task "sleep" in the process instance will take 2 minutes to complete.)
      5. Try refreshing the instance diagram a few times and wait for a minute or more.

      Actual result

      The following error will come up in the BC's server.log
      ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-27) Error from user: rhpamAdmin Error ID: 201142205 Location: ProcessInstances|ProcessInstanceListScreen[WProcessInstanceListBasicFiltersScreen,]$ProcessInstanceDetailsScreen Exception: Uncaught exception: org.kie.server.common.rest.NoEndpointFoundException:No available endpoints found

      On a side note, the kie-server API [2] will indeed return the correct process instance diagram while the long running task is getting executed.
      [2] /server/containers/

      {containerId}

      /images/processes/instances/

      {processInstanceId}

      Expected result

      Process diagram is not blank.
      No errors are printed in server.log.

      Show
      1. Import the attached project "fail-over-non-async.zip" into BC and deploy to kie-server 2. Start a process instance for the process definition "fail-over-non-async.long-wait" 3. Open the process instance diagram for the process instance that was started in step 2. 4. The diagram will be "blank" as shown in the attachment "Blank_Process_Instance_Diagram.png" (while the task "sleep" in the process instance will take 2 minutes to complete.) 5. Try refreshing the instance diagram a few times and wait for a minute or more. Actual result The following error will come up in the BC's server.log ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-27) Error from user: rhpamAdmin Error ID: 201142205 Location: ProcessInstances|ProcessInstanceListScreen [WProcessInstanceListBasicFiltersScreen,] $ProcessInstanceDetailsScreen Exception: Uncaught exception: org.kie.server.common.rest.NoEndpointFoundException:No available endpoints found On a side note, the kie-server API [2] will indeed return the correct process instance diagram while the long running task is getting executed. [2] /server/containers/ {containerId} /images/processes/instances/ {processInstanceId} Expected result Process diagram is not blank. No errors are printed in server.log.
    • ---
    • ---
    • 2020 Week 52-03 (from Dec 21), 2021 Week 04-06 (from Jan 25), 2021 Week 07-09 (from Feb 15), 2021 Week 10-12 (from Mar 8)

    Description

      When a process instance has a task/step that is long running, then its corresponding process diagram in business central shows up as "blank" (with an error [1] in BC's server.log), until that long running task is complete.

      [1] 13:29:47,319 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-21) Error from user: rhpamAdmin Error ID: 28471463 Location: ProcessInstances|ProcessInstanceListScreen[WProcessInstanceListBasicFiltersScreen,]$ProcessInstanceDetailsScreen Exception: Uncaught exception: org.kie.server.common.rest.NoEndpointFoundException:No available endpoints found
      13:30:02,049 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-21) Error from user: rhpamAdmin Error ID: 49560733 Location: ProcessInstances|ProcessInstanceListScreen[WProcessInstanceListBasicFiltersScreen,]$ProcessInstanceDetailsScreen Exception: Uncaught exception: org.kie.server.common.rest.NoEndpointFoundException:No available endpoints found
      13:30:02,986 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-21) Error from user: rhpamAdmin Error ID: 49569507 Location: ProcessInstances|ProcessInstanceListScreen[WProcessInstanceListBasicFiltersScreen,]$ProcessInstanceDetailsScreen Exception: Uncaught exception: org.kie.server.common.rest.NoEndpointFoundException:No available endpoints found
      13:30:25,099 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-20) Error from user: rhpamAdmin Error ID: 51497307 Location: ProcessInstances|ProcessInstanceListScreen[WProcessInstanceListBasicFiltersScreen,]$ProcessInstanceDetailsScreen Exception: Uncaught exception: org.kie.server.common.rest.NoEndpointFoundException:No available endpoints found
      13:39:56,582 ERROR [org.kie.workbench.common.services.backend.logger.GenericErrorLoggerServiceImpl] (default task-27) Error from user: rhpamAdmin Error ID: 201142205 Location: ProcessInstances|ProcessInstanceListScreen[WProcessInstanceListBasicFiltersScreen,]$ProcessInstanceDetailsScreen Exception: Uncaught exception: org.kie.server.common.rest.NoEndpointFoundException:No available endpoints found

      The expected behaviour is that BC process instance diagram viewer should show the process instance with the correct states of each steps and shouldn't be blank when there are long running steps in process instances.

      Attachments

        1. 20210315215924699.mp4
          6.68 MB
        2. fail-over-non-async.zip
          102 kB
        3. jbpm-9550-blankdiagram-error.webm
          1.08 MB
        4. RHPAM-3293.bpmn
          9 kB
        5. Selection_094.png
          Selection_094.png
          27 kB

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-3293 [GSS] (7.11.x) Business Central - Blank process diagram for processes with long running tasks

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBPM-9575 Unexpected system error after starting process instace

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

          Activity

            People

              xiabai@redhat.com Xiaofeng Bai
              xiabai@redhat.com Xiaofeng Bai
              Prashanth TS Prashanth TS (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: