tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ziggy <zigg...@gmail.com>
Subject Re: Accessing context information remotely - Context.getAvailable() etc.
Date Fri, 07 Jan 2011 11:53:46 GMT
Hi,

Will a "full JMX" be started on the Tomcat JVM or on the JVM in which i am
running the process to connect to the Tomcat instance? presumably if it is
the latter then it will shutdown once the client tool completes? The tool
should only take a few seconds to run on each iteration.

Thanks

On Fri, Jan 7, 2011 at 11:50 AM, Ziggy <ziggy25@gmail.com> wrote:

> 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.
>
> Thanks
>
>
> On Fri, Jan 7, 2011 at 11:42 AM, Rainer Jung <rainer.jung@kippdata.de>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:
>>
>>
>> http://tomcat.apache.org/tomcat-6.0-doc/manager-howto.html#Using_the_JMX_Proxy_Servlet
>>
>> Regards,
>>
>> Rainer
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>

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