Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-3916

Graph Failure Origin does not show any values in Runtime screen of Transactions

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.0.1.CR2, 7.0.1.GA
    • None
    • Web Console
    • None
    • EAP 7.0.1

    Description

      When Transaction statistics are enabled and I go to screen
      Server: Standalone Server    Monitor: Subsystems    Subsystem: Transactions
      I can see that graph Failure Origin shows no values - no graph is displayed.

      If some failure occurs the graph should be consistent with values besides Application Failures and Resource Failures.

      Please see example at attached print screen.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. HAL-1065 Graph Failure Origin does not show any values in Runtime screen of Transactions statistics

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-4753 Upgrade HAL from 2.8.25.Final to 2.8.26.Final

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

          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) JBEAP-2456 Transaction statistics screen troubles and unclarity

          • 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

              thofman Tomas Hofman
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: