-
Bug
-
Resolution: Done
-
Major
-
None
-
None
- The WildFly Console is not able to display the JMS Metrics.
http://localhost:9990/console/App.html#jms-metrics
- Where as the CLI command as following can show the JMS metrics properly.
[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/jms-queue=TestQ:read-resource(include-runtime=true,include-defaults=true) { "outcome" => "success", "result" => { "consumer-count" => 0, "dead-letter-address" => "jms.queue.DLQ", "delivering-count" => 0, "durable" => false, "entries" => ["java:jboss/exported/TestQ"], "expiry-address" => "jms.queue.ExpiryQueue", "message-count" => 1L, "messages-added" => 4L, "paused" => false, "queue-address" => "jms.queue.TestQ", "scheduled-count" => 0L, "selector" => undefined, "temporary" => false } }
- is duplicated by
-
HAL-401 JMS destination statistics are not shown on the admin console
- Resolved