Note that there are some explanatory texts on larger screens.

plurals
  1. PODoes Java 6 open a default port for JMX remote connections?
    primarykey
    data
    text
    <p>My specific question has to do with JMX as used in JDK 1.6: if I am running a Java process using JRE 1.6 with </p> <pre><code>com.sun.management.jmxremote </code></pre> <p>in the command line, does Java pick a default port for remote JMX connections?</p> <p>Backstory: I am currently trying to develop a procedure to give to a customer that will enable them to connect to one of our processes via JMX from a remote machine. The goal is to facillitate their remote debugging of a situation occurring on a real-time display console. Because of their service level agreement, they are strongly motivated to capture as much data as possible and, if the situation looks too complicated to fix quickly, to restart the display console and allow it to reconnect to the server-side.</p> <p>I am aware the I could run <a href="http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html" rel="noreferrer">jconsole</a> on JDK 1.6 processes and <a href="http://java.sun.com/javase/6/docs/technotes/tools/share/jvisualvm.html" rel="noreferrer">jvisualvm</a> on post-JDK 1.6.7 processes given physical access to the console. However, because of the operational requirements and people problems involved, we are strongly motivated to grab the data that we need remotely and get them up and running again.</p> <p>EDIT: I am aware of the command line port property </p> <pre><code>com.sun.management.jmxremote.port=portNum </code></pre> <p>The question that I am trying to answer is, if you do not set that property at the command line, does Java pick another port for remote monitoring? If so, how could you determine what it might be?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload