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

Improve monitoring of JMS pooled connection in JBoss CLI

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 11.0.0.Alpha1
    • 8.1.0.Final
    • JMS
    • None

    Description

      At the moment there is no way of monitoring pooled JMS connections in JBoss CLI. It would be nice if there was some information available similar to what is available for JDBC pools:

      "pool" => {
                "ActiveCount" => "0",
                "AvailableCount" => "0",
                "AverageBlockingTime" => "0",
                "AverageCreationTime" => "0",
                "CreatedCount" => "0",
                "DestroyedCount" => "0",
                "InUseCount" => "0",
                "MaxCreationTime" => "0",
                "MaxUsedCount" => "0",
                "MaxWaitCount" => "0",
                "MaxWaitTime" => "0",
                "TimedOut" => "0",
                "TotalBlockingTime" => "0",
                "TotalCreationTime" => "0",
                "statistics-enabled" => false
            }

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBJCA-1330 XA Stats not updated when the provided XAResource already implements XAResourceWrapper

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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7650 XA statistics are not updated for pooled-connection-factory resource

          • 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

              jmesnil1@redhat.com Jeff Mesnil
              rhn-support-toross Tom Ross
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: