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

Errors when deploying container to server template without Kie server connected

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • 7.33.0.Final
    • Workbench
    • NEW
    • NEW
    • Hide

      Deploy Workbench on EAP and start it.
      Open Execution servers perspective, create new Server Configuration (with all capabilities enabled).
      Open Design perspective, create new empty project.
      Build and install the project.
      Switch to Execution servers perspective, click on 'Add Deployment Unit'.
      Select built artifact => Workbench error is thrown.
      If you click on Continue and finish creating of new Deployment Unit then second error is shown in log.

      Show
      Deploy Workbench on EAP and start it. Open Execution servers perspective, create new Server Configuration (with all capabilities enabled). Open Design perspective, create new empty project. Build and install the project. Switch to Execution servers perspective, click on 'Add Deployment Unit'. Select built artifact => Workbench error is thrown. If you click on Continue and finish creating of new Deployment Unit then second error is shown in log.

    Description

      When user tries to deploy a new container into server template without any Kie server connected then this error is thrown - see workbench-stacktrace.txt

      Also when you finish the container deployment then this warning is shown in log:

      15:56:54,081 WARN  [org.jbpm.workbench.ks.integration.KieServerIntegration] (default task-3) Failed to create kie server client for container com.myspace:aaa:1.0.0-SNAPSHOT due to null

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2668 Errors when deploying container to server template without Kie server connected

          • 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

          Activity

            People

              eignatow Eder Ignatowicz
              ksuta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: