Also, we (of jetty) can only control what we expose for JMX for jetty classes, we can't control if a datasource exposes anything via JMX.
If there is something specifically in jetty that you want exposed via JMX let us know though, perhaps there is some room for our jndi bits to be exposed more/better jesse -- jesse mcconnell [email protected] On Wed, May 29, 2013 at 9:41 AM, Thomas Becker <[email protected]> wrote: > Hi Pooja, > > have you read this already? > > http://www.eclipse.org/jetty/**documentation/current/jmx-**chapter.html<http://www.eclipse.org/jetty/documentation/current/jmx-chapter.html> > > Cheers, > Thomas > Am 5/29/13 3:37 PM, schrieb Dilip-Mehta, Pooja: > >> Hi, >> >> I'm fairly new to jetty. >> >> I want to set up monitoring for jetty, esp. for data source and >> connections. >> >> I'm able to connect to jconsole successfully, but all it gives me are >> memory monitors. >> >> I know that some probes are available, but I would like to monitor using >> jmx itself. >> >> Could you please let me know how can I configure jetty to monitor data >> sources? >> >> Regards, >> >> Pooja Mehta >> >> >> >> ______________________________**_________________ >> jetty-users mailing list >> [email protected] >> https://dev.eclipse.org/**mailman/listinfo/jetty-users<https://dev.eclipse.org/mailman/listinfo/jetty-users> >> >> > ______________________________**_________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/**mailman/listinfo/jetty-users<https://dev.eclipse.org/mailman/listinfo/jetty-users> >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
