[
https://issues.jboss.org/browse/WFLY-5293?page=com.atlassian.jira.plugin....
]
Arto Huusko commented on WFLY-5293:
-----------------------------------
In your example either no invocations have been done, or EJB statistics gathering is not
enabled, and therefore methods is empty.
I tested a case where the cli does report usable statistics in the methods element, and
still the JMX attribute is useless as described.
So in case of the methods attribute the JMX translation does not work correctly.
EJB3 method invocation statistics exposed incorrectly through JMX
-----------------------------------------------------------------
Key: WFLY-5293
URL:
https://issues.jboss.org/browse/WFLY-5293
Project: WildFly
Issue Type: Bug
Components: JMX
Affects Versions: 9.0.1.Final
Reporter: Arto Huusko
Assignee: Kabir Khan
EJB3 method invocation statistics, that is the "methods" attribute in an EJB3
session JMX object is exposed as CompositeDataSupport object that has the expected keys
("execution-time", and so on), but
- the values for the keys are always null
- there is only a single CompositeDataSupport object even when the session has several
methods
- the method name is not available.
Possibly the invocation statistics should be exposed as an array of CompositeDataSupport
objects where one of the keys is the method name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)