Thanks for that - The client tool i am writing is running on the same machine as the application which is firewalled. There is no direct access to the webapp except via an AJP port which is only accessible via Apache Webserver.
Thanks On Sat, Jan 8, 2011 at 4:07 PM, Konstantin Kolinko <knst.koli...@gmail.com>wrote: > 2011/1/8 zigg...@gmail.com <zigg...@gmail.com>: > > Yes I guess you are right that launching the jmx every minute could be > expensive resourcewise... i am wondering whether it will be less expensive > if I just start a thread and same it up every minute... this way the jmx > engine will only be started once... > > One more word of caution: > JMX is effectively a low-level administrative interface. We compare it > to the "root" access sometimes. There are little (or no) barriers from > abusing it. > > Thus, if you allow external access through JMX, this access should be > controlled and secured. > > (I am sure that that is written somewhere on how to do that. It is not > a Tomcat-specific issue. Though I do not have a link ready.) > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
