logger命令执行成功, 实际项目的日志级别仍然是原来的级别
- Dominant language
- Java
- Stars
- 37.5k
- Forks
- 7.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 4
Description
- [ ] 我已经在 [issues](https://github.com/alibaba/arthas/issues) 里搜索,没有重复的issue。
### 环境信息
* `arthas-boot.jar` 或者 `as.sh` 的版本: arthas-all-3.6.1
* Arthas 版本: 3.6.1
* 操作系统版本: Linux version 3.10.0-1160.42.2.el7.x86_64
* 目标进程的JVM版本: OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)
* 执行`arthas-boot`的版本: arthas-all-3.6.1
arthas-spring-boot-starter: 3.3.6
### 重现问题的步骤
[arthas@15856]$ logger -c b4aac2 --name ROOT --level INFO
Update logger level success.
[arthas@15856]$ logger
name root
class org.apache.logging.log4j.core.config.LoggerConfig
classLoader sun.misc.Launcher$AppClassLoader@b4aac2
classLoaderHash b4aac2
level INFO
### 期望的结果
期望日志级别能动态修改成INFO级别
### 实际运行的结果
虽然命令执行成功, 实际项目仍然是DEBUG级别日志.
```
把异常信息贴到这里
```
Contributor guide
Research direction
Start with the `logger` command using the reported Arthas 3.6.1 environment and reproduce `logger -c b4aac2 --name ROOT --level INFO`, followed by `logger`. Trace the command's Log4j2 level-update handling and verify that the target application's effective logging changes from DEBUG to INFO, not only the reported logger configuration.
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
- Mostly clear
- Newbie friendliness
- 30/100