[jboss-jira] [JBoss JIRA] (AS7-4464) EJB3 deployment metrics missing

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/AS7-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764664#comment-12764664 ] 

RH Bugzilla Integration commented on AS7-4464:
----------------------------------------------

Jan Martiska <jmartisk at redhat.com> made a comment on [bug 911117|https://bugzilla.redhat.com/show_bug.cgi?id=911117]

Hi Carlo, I see that the changes are present in 6.1.0.ER4, but I only see method invocation metrics - execution time, invocation count and waiting time for each method. Nothing like cache size, passivated count, min/max invocation times, etc., as you specified in the first comment. Are you planning to add these? I am setting this to VERIFIED for now, so this should be considered just a reminder|question|whatever. Should you plan to add the mentioned metrics, feel free to reopen it. Thanks
                
> EJB3 deployment metrics missing
> -------------------------------
>
>                 Key: AS7-4464
>                 URL: https://issues.jboss.org/browse/AS7-4464
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.1.Final
>            Reporter: Stefan Negrea
>            Assignee: Carlo de Wolf
>            Priority: Critical
>              Labels: rhq
>             Fix For: 8.0.0.Alpha1
>
>
> The following metrics are missing from AS7 EJB3 subsystem from deployment when compared to AS5 exposed metrics:
> Stateless Session Bean
> Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
> Stateful Session Bean
> Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
> Cache Size - Cache Size
> Passivated Count - Passivated Count
> Total Size - Total Size

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira