[jboss-jira] [JBoss JIRA] Resolved: (JBAS-7107) Invocation statistics not collected on JMX based EJB2 managed components

[Lukas Krejci (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukas Krejci resolved JBAS-7107.
--------------------------------

    Resolution: Cannot Reproduce Bug


This seems to be a Jopr issue. Tracked by JOPR-280.

> Invocation statistics not collected on JMX based EJB2 managed components
> ------------------------------------------------------------------------
>
>                 Key: JBAS-7107
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7107
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-5.2.0.Beta1
>            Reporter: Lukas Krejci
>
> This was brought to light while investigating JOPR-280.
> During the Jopr AS5 plugin integration tests the metrics collection on EJB2 SFSBs, SLSBs, MDBs and Entity beans is tested.
> For session beans a single remote method is called 10 times on a single bean. The test then checks for CreateCount == 1 and for appropriate method invocation statistics.
> Both the create count and the invocation stats are always 0/empty. Note that this is also true for the MBeans of the session beans themselves when looking at the values in the jmx-console.
> For MDBs the collection statistics fails "most of the time". This might be because the JNDI name of a bean contains @object-id. Once some messages are delivered to the bean the @object-id part of the JNDI name changes from time to time. I suspect that with that change, the stats go as well.
> Entity bean metrics seem to be collected fine.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira