tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ziggy <>
Subject Re: Accessing context information remotely - Context.getAvailable() etc.
Date Fri, 07 Jan 2011 11:50:11 GMT
Yes i saw this earlier and would have been very usefull if i could have used
it. Unfortunately we dont deploy the manager or admin apps on the production
environments. These are only available on development and Test servers.


On Fri, Jan 7, 2011 at 11:42 AM, Rainer Jung <>wrote:

> On 06.01.2011 21:22, Ziggy wrote:
>> Please see my previous response re: open source tools. :)
>> As i mentioned earlier, the project that i need to deploy this tool will
>> not
>> allow any open source tool without it being approved which involves a long
>> security vetting process.
>> I appreciate that there are hundreds of tools out there that can do
>> exactly
>> what i am trying to do but sometimes there are reasons that those tools
>> cannot be used due to the nature of some projects.
> Using JMX as a protocol to remotely collect the info comes with the
> downside of starting a full JMX each time your cron job fires. There is a
> feature builtin into the Tomcat manager called jmxproxy. Via the jmxproxy
> you can query MBeans by HTTP and get back an easy to parse textual
> represenation of the attributes. That way you only need an HTTP client and
> parse a bit of text. It allows you to choose whatever client technology you
> like best. You can even configure a separate HTTP connector for
> administration and monitoring purposes, so that it will always be available
> independent of the load of the normal production connector.
> See:
> Regards,
> Rainer
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message