JRE环境下借助jattach使用arthas
- Dominant language
- Java
- Stars
- 37.6k
- Forks
- 7.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
- [x] 我已经在 [issues](https://github.com/alibaba/arthas/issues) 里搜索,没有重复的issue。
### 环境信息
* `arthas-boot.jar` 或者 `as.sh` 的版本: 4.0.3
* Arthas 版本: 4.0.3
* 操作系统版本: Linux rabbitmq1 5.10.0-60.18.0.50.oe2203.aarch64 SMP Wed Mar 30 02:43:08 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
* 目标进程的JVM版本: openjdk version "1.8.0_342"
* 执行`arthas-boot`的版本: 4.0.3
### 重现问题的步骤
1. 执行命令 *jattach 1854582 load instrument false "$PWD/arthas-agent.jar=--target-pid=1854582"* 加载agent
2. 第一天能成功加载 响应如下:
Connected to remote JVM
JVM response code = 0
0
且成功监听3658和8563端口, 再次通过java -jar $PWD/arthas-client.jar 可以成功连接进入console使用
3. 第二天不能加载成功, 响应如下:
Connected to remote JVM
JVM response code = 0
100
3658和8563端口未监听, 再次通过java -jar $PWD/arthas-client.jar 可以连接失败. 未找到任何arthas日志
### 期望的结果
1. 在仅存在JRE的环境中, 借助jattach加载agent的详细指导
2. 响应100表示什么意思? 相关日志在哪里?
3. 部分环境下通过 jattach 1854582 load instrument false "$PWD/arthas-agent.jar=ip=0.0.0.0" 可以全零监听部分情况不可以 这又是为何? 具体执行的参数有哪些?
### 实际运行的结果

Contributor guide
Research direction
Start by reproducing the jattach command against the JRE-based target described in the issue, comparing response codes 0 and 100. Check whether arthas-agent.jar starts the 3658 and 8563 listeners and where its logs are emitted; done means documenting the required parameters, explaining response 100, and covering the differing ip=0.0.0.0 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100