Monitoring the Tomcat 5.5 inside JBoss 4.0.x

Monitoring the Tomcat 5.5 inside JBoss 4.0.x

Hi,

I'm having trouble monitoring the Tomcat that lives inside JBoss.

Most likely related to the Tomcat "manager" webapp, which I can't seem to get to work properly - is the Tomcat inside JBoss somewhat crippled?

I've tried lots of things, including the AppManager troubleshooting tips (they seem to be for Tomcat+JBoss 3.x only?), running the JBoss "all" server config, reading the Apache Tomcat Config Reference and applying its manager related examples, but to no avail - I don't get this darn /manager thingie to work.
All other monitors on that machine (Linux, JBoss, JRE, Apache) are doing okay BTW.


Workaround for now: I mapped Tomcat's "status" servlet to /manager/status - this way I'm getting at least some values and am able to change settings of the Tomcat monitor (e.g. name, polling interval) in ApplicationsManager (which won't work if the /manager/ location isn't available at all)

But since the URLs queried by AppManager

/manager/status?XML=true
/manager/jmxproxy?qry=*%3Aj2eeType%3DServlet%2C*
/manager/html/list

won't yield any useful output (output is always the same HTML page as the /status servlet outputs) the Tomcat monitor in AppManager is missing some stuff.



So, if anyone has any info, if and how I can get the Tomcat monitoring to work properly - please share! :)





















                New to ADSelfService Plus?