On Tue, 18 Jun 2002, Glenn Nielsen wrote: > The current discussion about setting the maximum number of sessions > which can be created prompts me to raise an issue I have thought about > some but which I don't recall being discussed here yet. > > That is, instrumenting Tomcat so it can be monitored by external > tools (Introscope comes to mind). I have a number of instances of > Tomcat 4 in production now and so far have been able to get up to > a 4 week runtime before a failure forced me to stop/restart it. > This was on a site which handles 2-3 million JSP pages per month. > For production I really need hooks in Tomcat and tools which can > provide 24/7 monitoring and notification of problems. In addition > collect metrics so that the admin has real data to use for improving > the JVM settings, etc. > > Has anyone been working on this? If not, anyone interested in this?
Yes :-) The difficult part is to instrument the C side, and the jk2 scoreboard seems to resolve that. From java side - it's quite easy, all you need is add getters and collect the data, and JMX will expose them ( using per/thread structures - like notes associated with a request to avoid sync and keep it fast ). But I think we should wait for things to stabilise a bit, there are far too many things happening at once. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
