From 5fb1625ddacf7f27631f96b0b55d7d48e380b652 Mon Sep 17 00:00:00 2001 From: Joshua Levy Date: Tue, 14 Jul 2015 01:50:34 -0700 Subject: [PATCH] Fix up JDK language. Adjustments to #172 --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index e86b42e..af21393 100644 --- a/README.md +++ b/README.md @@ -233,8 +233,7 @@ Notes: - To know memory status, run and understand the output of `free` and `vmstat`. In particular, be aware the "cached" value is memory held by the Linux kernel as file cache, so effectively counts toward the "free" value. -- Java system debugging is a different kettle of fish, but a simple trick on Oracle's and some other JVMs is that you can run `kill -3 ` and a full stack trace and heap summary (including generational garbage collection details, which can be highly informative) will be dumped to stderr/logs. - Also default JDKs `jps`, `jstat`, `jstack`, `jmap` are quite usefull, take a look at their help. For more advanced cases use something like [SJK by Alexey Rogozin](https://github.com/aragozin/jvm-tools). +- Java system debugging is a different kettle of fish, but a simple trick on Oracle's and some other JVMs is that you can run `kill -3 ` and a full stack trace and heap summary (including generational garbage collection details, which can be highly informative) will be dumped to stderr/logs. The JDK's `jps`, `jstat`, `jstack`, `jmap` are useful. [SJK tools](https://github.com/aragozin/jvm-tools) are more advanced. - Use `mtr` as a better traceroute, to identify network issues.