If found an old post mentioning the same issue, but
no resolution or others. My config is pretty vanilly
except for setting the JMX options as part of
the normal Tomcat startup (CATALINA_OPTS)...
export CATALINA_OPTS=$CATALINA_OPTS
-Dcom.sun.management.jmxremote.port=
export
, the shutdown-VM will
unsuccessfully try to start a JMX server on port .
That's what taking so long.
Joe R. Lindsay wrote:
If found an old post mentioning the same issue, but
no resolution or others. My config is pretty vanilly
except for setting the JMX options as part of
the normal Tomcat
We have two webapps that communicate via jndi and
we need to have app2 wait for app1 to load before continuing.
Is there a way to force the order in which the webapps
are started?
Joe Lindsay
email: [EMAIL PROTECTED]
Users List
Subject: Re: webapp loading order...
On Tue, Aug 16, 2005 at 03:23:16PM -0700, Joe R. Lindsay wrote:
: We have two webapps that communicate via jndi and
: we need to have app2 wait for app1 to load before continuing.
: Is there a way to force the order in which the webapps
: are started
So, I have it up and running, but it seems that remote
monitoring requires a random 2nd data port
So, even when I set the remote jmx port to say 1234
after restarting tomcat I see it listening on port 1234
and something like 33051. This makes jmx remote a
bit difficult to use in a secure
