无法调试jvm?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the docker-debug container-attach behavior described by the repository and reproduce the issue using ps aux followed by jstack . Check why jstack reports that the target process is not responding or that HotSpot VM is not loaded; done means JVM debugging works for the affected container.
Written by the indexing model from the issue text.
Description
使用ps aux可以看到相关程序,但是使用 jstack 提示
Unable to open socket file: target process not responding or HotSpot VM not loaded
- Dominant language
- Go
- Stars
- 640
- Forks
- 40
- Avg merge
- 13h 26m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/prow#953 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
caddyserver/caddy#8046 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
L1 recommended for recruits
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/entangle bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100