Hi,
Not quite sure if I am off-track here, but:
If you want to avoid loosing statistics, you
might want to consider combining these two
methods into a single atomic call.
For example, if you want to count bean invocations,
and do not want to drop a single invocation from
your statistics.
If you get the stats, and then reset them, any
invocations between the two calls will neither
be in this stats, or the next one - they will
be utterly lost.
Not a good thing, if your customer pays per bean
invocation.
Best Regards,
Ole Husgaard.
Andreas Schaefer wrote:
>
> Hi Geeks
>
> Just to give you the opportunity to stop me before turning
> JBoss up side down here are my ideas to add Statistics
> into JBoss. The part I want to do is the EJB statistics for
> (at least right now) Entity Beans. The difficult part is to
> collect everything in a loose coupled system like JBoss.
>
> Therefore I suggest:
> - every statistics component must implement Monitorable
> - interface Monitorable contains the methods:
> - Statistic[] retrieve()
> - void reset()
> - in the Entity Bean case not only the Container has to
> implement Monitorable but also all the Interceptors.
> This is because some statistics asks for the method
> performance, Cache statistics etc.
>
> Statistic is a JSR-77 class which contains a name which
> would allow to map the delivered statistics to the one
> requested by JSR-77.
>
> Hope this is OK for all of you - Andy
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
