Uploaded image for project: 'KIE Cloud'
  1. KIE Cloud
  2. KIECLOUD-172

Monitoring console problems in rhpam-production-immutable environment

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.4.0.GA
    • 7.3.0.GA
    • Operator, RHPAM
    • None

    Description

      Monitoring console cannot correctly work with Kie servers deployed using S2I.
      The problem is that S2I build is using assets to build a kjar, but the kjar is stored directly in Kie server internal Maven repo, which is not accessible by Monitoring console.

      In case kjar contains custom class used in process the Monitoring console isn't able to start the process. In case user tries to start process using Monitoring console the ClassNotFoundException is thrown.

      The issue can be reproduced in Kie Operator or using templates.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2101 BC Monitoring fails to start a new process in an unmanaged immutable kieserver

          • 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
          is documented by

          Task - Represents a small unit of work that is not end-user facing. BXMSDOC-4145 Document use of custom classes in S2I+monitoring

          • 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.
          • Open
          is related to

          Bug - A problem that impairs or prevents the functions of the product. KIECLOUD-205 RHPAM Library Process Quickstarter JTA error

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RHPAM-2102 Create a Deployment Unit when a unmanaged immutable kieserver is connected to the BC

          • 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-2008 HTTP 503 error is shown in Monitoring console when Kie server is scaled to 0

          • 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

              rhn-support-zanini Ricardo Zanini Fernandes
              ksuta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: