On 23/12/2010 19:32, Adib wrote:
> Pid thanks or your comments below.
>
> Any idea why it was working just fine on a windows Vista machine but not on
> Windows 2008 R2. One of the main differences between the two machines is
> that the windows server has multiple IP addresses on the same network c
Pid thanks or your comments below.
Any idea why it was working just fine on a windows Vista machine but not on
Windows 2008 R2. One of the main differences between the two machines is
that the windows server has multiple IP addresses on the same network card,
could that be causing the agent to get
On 23/12/2010 10:01, Adib wrote:
> The local process option seems to be a hit and miss on various versions of
> windows, it was not working. Also the local process option only works if
> jconsole is running the same userid as process you want to connect to, which
> is not the case in my tomcat setu
On 23/12/2010 09:20, André Warnier wrote:
> Shortly :
> If you are local, then you can use the "Local process" option in jconsole.
But usually not if you're using the service wrapper, which masks* the
JVM process from the Attach API used in Java 6 to provide the local
processes.
* for want of a
The local process option seems to be a hit and miss on various versions of
windows, it was not working. Also the local process option only works if
jconsole is running the same userid as process you want to connect to, which
is not the case in my tomcat setup which is running as a service.
I teste
Shortly :
If you are local, then you can use the "Local process" option in jconsole.
Otherwise : as far as I remember, the jmx connection really uses 2 ports, not only the one
you obviously connect to. And that second port is random, which is what makes it difficult
to connect through a firewal
