On 22/10/2012 15:37, S Ahmed wrote: > I was thinking of using this: https://github.com/codahale/metrics > > Much easier to have this keep track of stats, and not having to rely on > jconsole just to get in insight.
Why is it easier to instrument Tomcat's code than to just use the JMX info that's already exposed? VisualVM & JConsole are not monitoring tools, they just display the info that's already exposed. Strongly recommend you at least familiarise yourself with what's in the Tomcat MBeans before you proceed. p > On Fri, Oct 19, 2012 at 5:37 PM, Pid <p...@pidster.com> wrote: > >> On 19/10/2012 16:18, Daniel Mikusa wrote: >>> On Oct 18, 2012, at 2:51 PM, S Ahmed wrote: >>> >>>> Hi, >>>> >>>> When using the jdbc connection pool library, would it be possible to >>>> somehow record the # of connections that are being used, >>>> when the # of connections in the pool are being saturated etc., or is >> that something that >>>> would have to be modified in the library itself? >>> >>> The connection pool publishes some statistics to JMX. An easy way to >> see them is connect with jconsole. If you need more advanced statistics, >> you could check / monitor them programmatically or use an existing >> monitoring tool. >> >> +1 Use VisualVM with the MBeans plugin or JConsole. >> >> >> p >> >>> Dan >>> >>> >>>> >>>> i.e. assuming I have can keep track of these counters, is there a way to >>>> monitor these events in the library or would the jdbc library itself >> need >>>> to be modified to expose these events? >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >> >> >> -- >> >> [key:62590808] >> >> > -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
