同步操作将从 唯品会/VJTools 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
VJDump comes as a handy script for collecting diagnostic data for JVM during urgent failures to allow for complete analysis later.
When major system failures occur for reasons not yet known, rebooting may be the only option to ease user complaints. There is so little time that even an experienced system admin might forget to pick up all he needs for offline analysis.
VJDump script is written to make us eaiser, which just packs outputs from T
jstack, jmap, gc logs into the form of a single zip file under /tmp/vjtools/vjdump
.
[Important]: Commands like jstack and jmap DO cause stop-of-the-world of the target app. Make sure the target app is isolated from user access before you run this full check in production.
Items to be collected by VJDump are:
jstack -l $PID
vjtop.sh -n 1 -d 3 $PID
(enabled when you have our vjtop installed and
have the folder of vjtop.sh appended to the PATH environment variable)jmap -histo $PID
& jmap -histo:live $PID
jmap -dump:live,format=b,file=${DUMP_FILE} $PID
Use the following commands under the same user who started the target process and collect results in /tmp/vjtools/vjdump
.
# collect dignostics for target $pid
vjdump.sh $pid
# include heap dump also via jmap -dump:live, might take longer
vjdump.sh --liveheap $pid
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。