xmengnet/the-art-of-command-line
1
0
Fork 0
mirror of https://github.com/xmengnet/the-art-of-command-line.git synced 2024-12-24 04:26:30 +08:00
Code Issues Projects Releases Packages Wiki Activity

Fix up JDK language.

Browse source 
Adjustments to #172
This commit is contained in:
Joshua Levy 2015-07-14 01:50:34 -07:00
parent b559d754ee
commit 5fb1625dda
1 changed files with 1 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
README.md
View file

@ -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 <pid>` 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 <pid>` 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.