Paolo, You could get mbean, attribute, and operation descriptions by using JConsole to connect to Jetty's MBeanServer.
-Michael On Thu, Jun 16, 2011 at 2:30 PM, Paulo Silveira < [email protected]> wrote: > 2011/6/16 Michael Gorovoy <[email protected]> > > > > There's a new Jetty module being worked on right now > (see JETTY-1375) that will provide RESTful interface to the JMX MBeans. You > could find the source code for it here. > > Thanks Michel. Is there any documentation about these Jetty's JMX beans: > > public static final String JETTY_SERVER_MBEAN = > "org.eclipse.jetty.server:type=server,id=0"; > public static final String JETTY_SERVER_MBEANID1 = > "org.eclipse.jetty.server:type=server,id=1"; > > > or even others? > thanks > Paulo > > > > -Michael > > On Thu, Jun 16, 2011 at 11:59 AM, Otis Gospodnetic < > [email protected]> wrote: > >> > >> Hi Paulo, > >> I think you get that from http://sematext.com/spm/index.html (it's > currently free and even when non-free plans are introduced, the intro plan > will stay free). The service is not 100% polished, but will give you > information about the OS and the JVM, including memory (RAM and heap) and > JVM threads. > >> > >> We'd love to get more Jetty-specific metrics from JMX in there, so if > anyone has interest, we'd love to hear what aspects of Jetty people like to > monitor. I'm all ears/eyeballs! > >> > >> Otis > >> ---- > >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch > >> Lucene ecosystem search :: http://search-lucene.com/ > >> > >> ________________________________ > >> From: Paulo Silveira - Caelum <[email protected]> > >> To: [email protected] > >> Sent: Thursday, June 16, 2011 11:37 AM > >> Subject: [jetty-users] monitoring jetty threads and sockets > >> > >> Hello > >> I would like to monitor simple data from jetty, using only a web > context. Is there anything like that, besides the codehaus documentation > page about java-monitor? > >> > >> Basic info, as numbers from ThreadMXBean, MemoryUsage and so one. > Tomcat/Lambda probe also lists each thread status and stacktrace, making > possible to easily detect even deadlocks. > >> > >> Through java.lang.management we can get all this data, but using jetty's > internal API could we get even more important info, as number of sockets > waiting/ready for the selector? > >> > >> thanks > >> -- > >> Paulo Silveira > >> Caelum | Ensino e Inovação > >> www.caelum.com.br > >> > >> > >> _______________________________________________ > >> jetty-users mailing list > >> [email protected] > >> https://dev.eclipse.org/mailman/listinfo/jetty-users > >> > >> > >> > >> _______________________________________________ > >> jetty-users mailing list > >> [email protected] > >> https://dev.eclipse.org/mailman/listinfo/jetty-users > >> > > > > > > _______________________________________________ > > jetty-users mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/jetty-users > > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
