I think the only possibility in order to fix RMI server port behind a
firewalled system is to use JMX Remote Lifecycle Listener in server.xml and
add catalina-jmx-remote.jar in lib folder.
I used it for remote jvm monitoring and now works fine.
You can read procedure here
http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html
regards
On 12 May 2010 13:40, emerson cargnin <echofloripa.y...@gmail.com> wrote:
> Thanks Chuck
>
> But I meant in changing this random port to a specific one without having
> to
> change the server.xml to add a new listener and jars.
>
> regards
> Emerson
>
> On 9 April 2010 02:12, Caldarale, Charles R <chuck.caldar...@unisys.com
> >wrote:
>
> > On Apr 8, 2010, at 12:59, "emerson cargnin"
> > <echofloripa.y...@gmail.com> wrote:
> >
> > > I would be great if that could be configured directly in the
> > > properties
> >
> > I suspect that you can. Most attribute values in server.xml can be
> > encoded as ant-style system property references:
> >
> > attr="${my.property}"
> >
> > - Chuck
> >
> > >>
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> >
>
