Remy, Could you move the manager servlets to webapps/manager ? As you can see, I can't touch build.xml without breaking something :-).
I would also like to move the coyote/tomcat5 code in catalina - and eventually coyote/tomcat4 to jakarta-tomcat-4 and same for 3.3 ( preserving the same package names, I just want the code to be included in catalina.jar and in catalina sources ). The problem is that tomcat-coyote.jar is now dependent on all tomcats. Costin Jean-Francois Arcand wrote: > Hi Remy, > > the servlet doesn't compile with JDK 1.3.x : > >>StatusManagerServlet.java:274: cannot resolve symbol >> [javac] symbol : method maxMemory () >> [javac] location: class java.lang.Runtime >> [javac] writer.print(Runtime.getRuntime().maxMemory()); >> [javac] ^ >> [javac] Note: Some input files use or override a deprecated API. >> [javac] Note: Recompile with -deprecation for details. >> [javac] 1 error >> > This method is only available with JDK 1.4 +. > > > -- Jeanfrancois > > Remy Maucherat wrote: > >> Remy Maucherat wrote: >> >>> Hi, >>> >>> I proposed that to Costin a few days ago, but got not so enthusiastic >>> comments. >>> The idea would be to add a new monitor servlet to the manager webapp. >>> It would generate data similar to >>> http://www.apache.org/server-status. It would mostly (exclusively ?) >>> use JMX to retrieve the components statistics. >>> >>> That's not a high priority task for me, but something I'd like to get >>> done eventually, and I'm looking for some feedback. I understand that >>> there are existing agents for JMX that can be used to provide more >>> powerful remote access to the statistics (HTTP, RMI, etc), but these >>> tools do not have the ability to give a user a quick and >>> comprehensive look at the Tomcat status (although they allow much >>> more complex operations, and it's not my objective to replace them). >> >> >> I've committed a rough version of the monitoring servlet. It will >> display status information for all Coyote connectors, using JMX >> exclusively. I don't think there's any statistic missing (the amount >> of meaningful status information available to a Java program is >> definitely much lower than for a native Unix program, hence the >> "simpler" look when compared to the Apache status). >> >> The thing is very rough, and could use contributions (hint, hint) :) >> >> As for using it, the monitor servlet is linked from the default Tomcat >> welcome page. It currently requires the same credentials as the rest >> of the manager webapp to access. >> >> Remy >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
