[
https://issues.jboss.org/browse/WFLY-5293?page=com.atlassian.jira.plugin....
]
Stefano Coletta edited comment on WFLY-5293 at 1/14/16 7:08 AM:
----------------------------------------------------------------
I've found the same problem on wildfly-8.2.0.FInal. Could you confirm me the bug
affect also wildfly-8.2.0.Final?
I didn't understand the problem affect only the jconsole gui (where I don't see
the ejb3 method statistics) or the jmx bean who reads from cli command the statistics
value.
was (Author: stecolet):
I've found the same problem on wildfly-8.2.0.FInal. Could you confirm me the bug
affect also wildfly-8.2.0.Final?
Thanks.
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)