Hi,
I think you should add this line
-Djava.rmi.server.hostname=192.168.1.12 like this
-Dcom.sun.management.jmxremote.port=8080 \
-Dcom.sun.management.jmxremote.ssl=false \
-Dcom.sun.management.jmxremote.authenticate=true \
-Djava.rmi.server.hostname=192.168.1.12
Thanks for answer, but don't solve. I executed jconsole in debug mode and
the eception stack is this:
java.rmi.ConnectException: Connection refused to host: xxx.xxx.xxx.xxx;
nested exception is:
java.net.ConnectException: Connection timed out: connect
at
On 14/12/2009 10:04, Paolo Santarsiero wrote:
Thanks for answer, but don't solve. I executed jconsole in debug mode and
the eception stack is this:
Firewall settings interfering?
Is the server actually listening on the port you set?
p
java.rmi.ConnectException: Connection refused to host:
I use 8080 port because it's sure open on server (I used it for tomcat
direct access).
2009/12/14 Pid p...@pidster.com
On 14/12/2009 10:04, Paolo Santarsiero wrote:
Thanks for answer, but don't solve. I executed jconsole in debug mode and
the eception stack is this:
Firewall settings
Paolo Santarsiero wrote:
I use 8080 port because it's sure open on server (I used it for tomcat
direct access).
I believe the monitor port has to be a different one from the http
request port, so if 8080 is the one your app is listening on, it won't
work for monitoring.
2009/12/14 Pid
From: Kockert, Timo [mailto:timo.kock...@adesso-mobile.de]
Subject: AW: remote monitoring JVM by VisualVM
You forgot -Dcom.sun.management.jmxremote.
-Dcom.sun.management.jmxremote \
-Dcom.sun.management.jmxremote.port=port \
-Dcom.sun.management.jmxremote.authenticate=false \
From: David kerber [mailto:dcker...@verizon.net]
Subject: Re: remote monitoring JVM by VisualVM
I believe the monitor port has to be a different one from the http
request port, so if 8080 is the one your app is listening on, it won't
work for monitoring.
The OP already stated that he
...@verizon.net]
Subject: Re: remote monitoring JVM by VisualVM
I believe the monitor port has to be a different one from the http
request port, so if 8080 is the one your app is listening on, it won't
work for monitoring.
The OP already stated that he disabled the HTTP Connector.
- Chuck
From: Paolo Santarsiero [mailto:paolo.santarsi...@gmail.com]
Subject: Re: remote monitoring JVM by VisualVM
I use 8080 port because it's sure open on server (I used it for tomcat
direct access).
Unfortunately, JMX requires an additional, dynamically assigned port, making it
difficult
Many thanks Chuck, I think this can solve my problem. How can I integrate
this Listener in my production Tom?
2009/12/14 Caldarale, Charles R chuck.caldar...@unisys.com
From: Paolo Santarsiero [mailto:paolo.santarsi...@gmail.com]
Subject: Re: remote monitoring JVM by VisualVM
I use 8080
From: Paolo Santarsiero [mailto:paolo.santarsi...@gmail.com]
Subject: Re: remote monitoring JVM by VisualVM
How can I integrate this Listener in my production Tom?
The general building-from-source instructions are here:
http://tomcat.apache.org/tomcat-6.0-doc/building.html
It's easy
11 matches
Mail list logo