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

User Task with a subform - Process Diagram error

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 7.18.0.Final
    • Fix Version/s: 7.18.0.Final
    • Component/s: Console
    • Labels:
      None
    • Sprint:
      2019 Week 08-10
    • Story Points:
      3
    • Steps to Reproduce:
      1. start a process instance
      2. navigate to the process instance details
      3. close the error dialog
      4. navigate to Diagram tab
      5. see the second dialog
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      When entering Process Instance details page an Unexpected error appears. It seems that the failure is dependent on process definition. This report is for a process with User Task that has a complex object as one of its variables.

      details of the error
      {"ToSubject":"org.jbpm.workbench.pr.service.ProcessRuntimeDataService:RPC.getProcessInstanceDiagramSummary:org.jbpm.workbench.pr.model.ProcessInstanceKey::59:RespondTo:RPC"} | Uncaught exception: Client-side exception occurred although RPC call succeeded. Caused by: (TypeError) : c.node(...) is null
      

      There is an error log in the server.log:

      2019-02-19 10:48:51,215 WARN  [org.kie.server.services.jbpm.ui.ImageServiceBase] (default task-8) Could not find SVG image file for process 'console.SubformTest' within container consoleContainerID
      2019-02-19 10:48:51,216 WARN  [org.jbpm.workbench.pr.backend.server.RemoteProcessImageServiceImpl] (default task-18) Failed to retrieve process instance image: Unexpected HTTP response code when requesting URI 'http://localhost:8080/kie-server/services/rest/server/containers/consoleContainerID/images/processes/instances/1'! Error code: 404, message: "Image for process instance id 1 not found"
      

      When user closes the dialog and navigates to the Diagram tab, there's slightly different error details description:

      Uncaught exception: Exception caught: (TypeError) : c.node(...) is null Caused by: (TypeError) : c.node(...) is null
      

      and in this case, there's no additional error in the server.log

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  cristiano.nicolai Cristiano Nicolai
                  Reporter:
                  jstastny Jan Stastny
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: