On 26/05/2011 21:50, André Warnier wrote: > André Warnier wrote: >> Pid wrote: >>> On 26/05/2011 20:16, Caldarale, Charles R wrote: >>>>> From: André Warnier [mailto:a...@ice-sa.com] Subject: Monitoring >>>>> memory usage of JVM >>>>> I am thinking of a couple of command-line options for the JVM, >>>>> to dump for example some information each time a GC happens, >>>> Try -verbose:gc and -Xloggc:<file_path_of_your_choice> >>> >>> The jmap & jstat commands shipped with the JDK are also useful. >>> >>> >> Thanks to both. >> I'll try these out. >> > For now, I have used the "-verbose:gc and -Xloggc:" command-line > options, and added the jmap command into one of the other monitoring > shell scripts I created. > I'll have to wait for the next GC to see the output of the switches. As > the application isn't doing anything right now, that could take a while. > > But a question about "jstat" in the meantime : > In the documentation of jstat, it has this to say about the /lvmid/ part : > > port > The default port for communicating with the remote server. If the > hostname is omitted or the protocol specifies an optimized, local > protocol, then port is ignored. Otherwise, treatment of the port > parameter is implementation specific. For the default rmi protocol, the > port indicates the port number for the rmiregistry on the remote host. > If port is omitted, and protocol indicates rmi, then the default > rmiregistry port (1099) is used. > > Is this the same port which I otherwise set for jconsole, iow via the > option : > -Dcom.sun.management.jmxremote.port=pppp
Yes, AFAIK. There's also a companion utility 'jstatd'. p
signature.asc
Description: OpenPGP digital signature
