Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14889

Enable datasource statistics is not handled properly in management console

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 23.0.2.Final
    • Management, Web Console
    • None
    • Hide
      1. Download and build hibernate quickstart: https://github.com/wildfly/quickstart/tree/23.x/hibernate
      2. Download Wildfly 23
      3. Edit standalone.xml: change statistics-enabled in datasource to: 
        statistics-enabled="${env.DATASOURCE_STATISTICS:true}"
      4. Run wildfly and go to management console to access datasource statistics.
      Show
      Download and build hibernate quickstart:  https://github.com/wildfly/quickstart/tree/23.x/hibernate Download Wildfly 23 Edit standalone.xml: change  statistics-enabled in datasource to: statistics-enabled= "${env.DATASOURCE_STATISTICS: true }" Run wildfly and go to management console to access datasource statistics.
    • Undefined

    Description

      When we want to configure datasource statistics: statistics-enabled management UI will not handle environment properties correctly. When statistics are enabled by environment variables, UI will show that they are disabled and we need to click on enable statistics button to display them (statistics are gathered but UI don't know it). After clicking on enable statistics button, true will be hardcoded in standalone instead of environment variable which breaks configuration.

      We should handle environment variables correctly here to display statistics immediately.
      Issue occurs on the newest 23 version, but was discovered also on older versions so this is something old.

      Attachments

        Issue Links

          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) HAL-1573 Enhance evaluation of boolean expressions

          • 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

          Activity

            People

              hpehl@redhat.com Harald Pehl
              pjowko Piotr Jówko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: