We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jdk:8 arthas:3.7.1 容器技术:docker
1、通过tunnel server连接容器内部的arthas agent,用完之后在web页面上输入stop,发现arthas agent进程没有退出,使用ps -ef命令查看,发现原先的arthas agent进程变成了 pid [java] 的格式
下面启停过两次,于是有两个残留进程:
2、如果不使用tennel server,而是直接使用在容器内部启动arthas agent时的交互界面,使用完输入stop,就没上面的问题!
过tunnel server连接容器内部的arthas agent,用完之后在web页面上输入stop,希望arthas agent进程完全退出、不要有残留进程!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
环境信息
jdk:8
arthas:3.7.1
容器技术:docker
重现问题的步骤
1、通过tunnel server连接容器内部的arthas agent,用完之后在web页面上输入stop,发现arthas agent进程没有退出,使用ps -ef命令查看,发现原先的arthas agent进程变成了 pid [java] 的格式
下面启停过两次,于是有两个残留进程:
![image](https://private-user-images.githubusercontent.com/33950671/339307605-0fcfb425-ae2f-455c-912c-6ee618cbc4ec.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk2MTEwODAsIm5iZiI6MTcxOTYxMDc4MCwicGF0aCI6Ii8zMzk1MDY3MS8zMzkzMDc2MDUtMGZjZmI0MjUtYWUyZi00NTVjLTkxMmMtNmVlNjE4Y2JjNGVjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI4VDIxMzk0MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWMyN2FhYjdiZmM1OTc4ZjM0MmYzMmJhYzk4M2RhMWU0NWY3ZTAwYWRlODJjODBiMzY0NzgzNTUwNmQxYWQ0NWEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.tPMZ7H7cvQ1Ox5fQne0lOKZ5Po6POPUj_kbpnk4SX54)
2、如果不使用tennel server,而是直接使用在容器内部启动arthas agent时的交互界面,使用完输入stop,就没上面的问题!
期望的结果
过tunnel server连接容器内部的arthas agent,用完之后在web页面上输入stop,希望arthas agent进程完全退出、不要有残留进程!
The text was updated successfully, but these errors were encountered: