Nice try, but unfortunately does not work... ;o) What I want to do is to use the mx4j features implemented in Tomcat to collect statistical information and I need to move the jk2.properties file for a security issue.
By the way this is not my only problem, for example: the mx4j functionality embedded in Tomcat will start up an internal rmiregistry service at port 1099 (that seems not to be configurable). This also means that the server running Tomcat cannot have a separate rmiregistry server running on port 1099. I spent some time looking on the web for information on this topic, but I got the impression that the not so many people are interested in it or, may be, that this technology is still too young. Any suggestion is wellcome. Bye, Paolo Martinelli IrisCube Reply S.p.A. -----Original Message----- From: news on behalf of Bill Barker Sent: Sun 6/6/2004 07:56 To: [EMAIL PROTECTED] Subject: Re: jk2.properties I've never tried it, but you should be able to set jkHome="/path/to/new/home" on the Connector element to have Tomcat look for /path/to/new/home/conf/jk2.properties. Of course, Tomcat will also use this as the base for any other relative file references (e.g. the unix-socket file). "Martinelli Paolo A." <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Hi all, I need to move the jk2.properties file from the "standard" location, does anyone knows how to do it??? Thanks, Paolo Martinelli IrisCube Reply S.p.A. --------------------------------------------------------------------- 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]
