> 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
I
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
> > From: Paolo Santarsiero [mailto:paolo.santarsi...@gmail.com]
> > Subject: Re: remote monitoring JVM by VisualVM
> >
> > I us
> 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,
bject: 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
> 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
> 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= \
> -Dcom.sun.manag
You forgot "-Dcom.sun.management.jmxremote".
Like:
-Dcom.sun.management.jmxremote \
-Dcom.sun.management.jmxremote.port= \
-Dcom.sun.management.jmxremote.authenticate=false \
-Dcom.sun.management.jmxremote.ssl=false
Greetings,
Timo
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
I use 8080 port because it's sure open on server (I used it for tomcat
direct access).
2009/12/14 Pid
> 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
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:
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 sun.rmi.transport.tcp.TCPEndpoint.newSocket
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
Hello, I'm tryng to monitor my JVM and so Tomcat HeapMemory usage by remote
access using VisualVM. I configured all, but my client always display an
error message (" Cannoct connect using
service:jmx:rmi:///jndi/rmi://xxx.xxx.xxx.xxx.:8080:jmxrmi").
I added in catalina.sh this Java options:
elif [
13 matches
Mail list logo
