You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use the command ./profiler.sh -e cpu,alloc,lock -o jfr --loop 60s -f %n{10000}.jfr --fdtransfer 407234 to profile my jvm process,the profiler output only one file and then stopped. I find that this is caused by the function "single_pid_server" in "fdtransferServer.cpp" source file, because it handle only one connection and then exit immediately, the subsequent connection from the profiler will be refused.
Is there any idea to avoid it.
When I use the command
./profiler.sh -e cpu,alloc,lock -o jfr --loop 60s -f %n{10000}.jfr --fdtransfer 407234
to profile my jvm process,the profiler output only one file and then stopped. I find that this is caused by the function "single_pid_server" in "fdtransferServer.cpp" source file, because it handle only one connection and then exit immediately, the subsequent connection from the profiler will be refused.Is there any idea to avoid it.
The captured log is like below:
The text was updated successfully, but these errors were encountered: