We are using J-Run 3.0 and I'm a little concerned about not having any
diagnostic information about the state of the servlet engine and the jvm at
runtime.

Didn't Sun remove the ability to get session information from the
ServletContext object? I want to write an servlet that monitors session
usage across out application.

What do folks use to keep an eye on background threads, servlet instances
etc etc?

Are web application writes suppose to capture all this informatoin
themselves now that Sun have removed the APIs to get at this stuff as of
2.2?



---
Robert Nicholson
Email: [EMAIL PROTECTED]
AOL  : rydmerlin

===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:

 http://java.sun.com/products/jsp/faq.html
 http://www.esperanto.org.nz/jsp/jspfaq.html
 http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
 http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets

Reply via email to