Jconsole and remote monitoring

Discussion:

daad\@libero\.it

2007-05-01 22:42:23 UTC

this is the process detail:

/usr/lib/jvm/java-6-sun/bin/java -Xms32M -Xmx32M -verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+HeapDumpOnOutOfMemoryError -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=7019 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/home/xx/tomcat/common/endorsed -classpath :/home/xx/tomcat/bin/bootstrap.jar:/home/xx/tomcat/bin/commons-logging-api.jar -Dcatalina.base=/home/xx/tomcat -Dcatalina.home=/home/xx/tomcat -Djava.io.tmpdir=/home/xx/tomcat/temp org.apache.catalina.startup.Bootstrap start

i run jconsole from last 1.6 jdk and use 192.168.0.5:7019 to connect, after some seconds it tell that connection failed: the connection did not succeed.

Since tomcat is running, from my windows box i can access to 192.168.0.5:8080 page, and if i start a jhat server i can reach it, so router configs works.
I tried to disable windows firewall and router firewall too: same behaviour.
If i don't start tomcat on the 192.168.0.5, jconsole doesn't even try to connect, it tell me connection refused, so i must miss any setting..

Any help please?

------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/

---------------------------------------------------------------------
To start a new topic, e-mail: ***@tomcat.apache.org
To unsubscribe, e-mail: users-***@tomcat.apache.org
For additional commands, e-mail: users-***@tomcat.apache.org

daad\@libero\.it

2007-05-01 23:01:49 UTC

Permalink

-Djava.rmi.server.hostname=192.168.0.5 was needed to connect since i'm under NAT.

maybe it's usefull for anybody else
bye

Post by daad\@libero\.it
/usr/lib/jvm/java-6-sun/bin/java -Xms32M -Xmx32M -verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+HeapDumpOnOutOfMemoryError -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=7019 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/home/xx/tomcat/common/endorsed -classpath :/home/xx/tomcat/bin/bootstrap.jar:/home/xx/tomcat/bin/commons-logging-api.jar -Dcatalina.base=/home/xx/tomcat -Dcatalina.home=/home/xx/tomcat -Djava.io.tmpdir=/home/xx/tomcat/temp org.apache.catalina.startup.Bootstrap start
i run jconsole from last 1.6 jdk and use 192.168.0.5:7019 to connect, after some seconds it tell that connection failed: the connection did not succeed.
Since tomcat is running, from my windows box i can access to 192.168.0.5:8080 page, and if i start a jhat server i can reach it, so router configs works.
I tried to disable windows firewall and router firewall too: same behaviour.
If i don't start tomcat on the 192.168.0.5, jconsole doesn't even try to connect, it tell me connection refused, so i must miss any setting..
Any help please?
------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
---------------------------------------------------------------------

------------------------------------------------------
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/

---------------------------------------------------------------------
To start a new topic, e-mail: ***@tomcat.apache.org
To unsubscribe, e-mail: users-***@tomcat.apache.org
For additional commands, e-mail: users-***@tomcat.apache.org

daad\@libero\.it

2007-05-02 14:27:20 UTC

Permalink

Now jconsole works but when i shut it down with /bin/./shutdown.sh i get this error:

Errore: Eccezione dell'agente : java.rmi.server.ExportException: Port already in use: 7019; nested exception is:
java.net.BindException: Address already in use

and tomcat doesn't shut down properly.
I added the "-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=7019 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=192.168.0.5" in the /bin/catalina.sh file with:

export JAVA_OPTS = "-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=7019 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=192.168.0.5"

is there any way i can fix this issue?
thanks

Post by daad\@libero\.it
-Djava.rmi.server.hostname=192.168.0.5 was needed to connect since i'm under NAT.
maybe it's usefull for anybody else
bye

Rainer Jung

2007-05-02 16:09:13 UTC

Permalink

You neded to change your start/stop scripts, so that they use the
management parameters only in the starting case and not in the stopping
case (define a new variable and add it in bin/catalina.sh to the "start"
case.

Post by daad\@libero\.it
java.net.BindException: Address already in use
and tomcat doesn't shut down properly.
export JAVA_OPTS = "-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=7019 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=192.168.0.5"
is there any way i can fix this issue?
thanks

---------------------------------------------------------------------
To start a new topic, e-mail: ***@tomcat.apache.org
To unsubscribe, e-mail: users-***@tomcat.apache.org
For additional commands, e-mail: users-***@tomcat.apache.org

Peter Rossbach

2007-05-02 19:02:20 UTC

Permalink

Please use CATALINA_OPTS to set jmx options. The catalina.sh stop
command use only JAVA_OPTS and not CATALINA_OPTS.
Peter

Post by Rainer Jung
You neded to change your start/stop scripts, so that they use the
management parameters only in the starting case and not in the
stopping
case (define a new variable and add it in bin/catalina.sh to the "start"
case.

Post by daad\@libero\.it
java.net.BindException: Address already in use
and tomcat doesn't shut down properly.
I added the "-Dcom.sun.management.jmxremote -
Dcom.sun.management.jmxremote.port=7019 -
Dcom.sun.management.jmxremote.ssl=false -
Dcom.sun.management.jmxremote.authenticate=false -
Djava.rmi.server.hostname=192.168.0.5" in the /bin/catalina.sh
export JAVA_OPTS = "-Dcom.sun.management.jmxremote -
Dcom.sun.management.jmxremote.port=7019 -
Dcom.sun.management.jmxremote.ssl=false -
Dcom.sun.management.jmxremote.authenticate=false -
Djava.rmi.server.hostname=192.168.0.5"
is there any way i can fix this issue?
thanks

---------------------------------------------------------------------

Rainer Jung

2007-05-03 06:28:49 UTC

Permalink

Thank's for reminding me, I forgot. But I think he uses 5.5.9 (very
outdated). CATALINA_OPTS was used for start and stop until 5.5.20, and
with 5.5.21 we switched to only using it for startup.

Post by Peter Rossbach
Please use CATALINA_OPTS to set jmx options. The catalina.sh stop
command use only JAVA_OPTS and not CATALINA_OPTS.
Peter

daad\@libero\.it

2007-05-02 21:13:21 UTC

Permalink

thank you.

Post by Rainer Jung
You neded to change your start/stop scripts, so that they use the
management parameters only in the starting case and not in the stopping
case (define a new variable and add it in bin/catalina.sh to the "start"
case.

---------------------------------------------------------------------