Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The relevant documentation can be found here:</p> <p><a href="http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html" rel="noreferrer">http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html</a></p> <p>Start your program with following parameters:</p> <pre class="lang-none prettyprint-override"><code>-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false </code></pre> <p>For instance like this:</p> <pre class="lang-none prettyprint-override"><code>java -Dcom.sun.management.jmxremote \ -Dcom.sun.management.jmxremote.port=9010 \ -Dcom.sun.management.jmxremote.local.only=false \ -Dcom.sun.management.jmxremote.authenticate=false \ -Dcom.sun.management.jmxremote.ssl=false \ -jar Notepad.jar </code></pre> <p><code>-Dcom.sun.management.jmxremote.local.only=false</code> is not necessarily required but without it, it doesn't work on Ubuntu. The error would be something like this:</p> <pre class="lang-none prettyprint-override"><code>01 Oct 2008 2:16:22 PM sun.rmi.transport. customer .TCPTransport$AcceptLoop executeAcceptLoop WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=37278] throws java.io.IOException: The server sockets created using the LocalRMIServerSocketFactory only accept connections from clients running on the host where the RMI remote objects have been exported. at sun.management.jmxremote.LocalRMIServerSocketFactory$1.accept(LocalRMIServerSocketFactory.java:89) at sun.rmi.transport. customer .TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:387) at sun.rmi.transport. customer .TCPTransport$AcceptLoop.run(TCPTransport.java:359) at java.lang.Thread.run(Thread.java:636) </code></pre> <p>see <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6754672" rel="noreferrer">http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6754672</a></p> <p><strong>Also be careful with <code>-Dcom.sun.management.jmxremote.authenticate=false</code></strong> which makes access available for anyone, but if you only use it to track the JVM on your local machine it doesn't matter.</p> <p><strong>Update</strong>:</p> <p>In some cases I was not able to reach the server. This was then fixed if I set this parameter as well: <code>-Djava.rmi.server.hostname=127.0.0.1</code></p>
    singulars
    1. This table or related slice is empty.
    1. POHow to activate JMX on my JVM for access with jconsole?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJoshua Taylor
    1. USMauli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to activate JMX on my JVM for access with jconsole?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe -Dcom.sun.management.jmxremote.local.only=false is needed on Centos now as well
      singulars
      1. PO
      1. USLenW
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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