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
hey, I' m using async-profiler when [/tmp/.java_pidXX] file is missing, that doesn't work obviously. And I found that message from stack overflow:
"/tmp/.java_pid socket is used by HotSpot [Dynamic Attach](http://openjdk.java.net/groups/hotspot/docs/Serviceability.html#battach) mechanism. It is the way how jstack and other utilities communicate with JVM.
You cannot change the path - it is hardcoded in JVM source code. Neither you can force JVM to regenerate it, because the Attach Listener is initialized only once in HotSpot lifetime."1
So I'm thinking is there any possible way(may be a tricky/geek way) that we can recover or regenerate this file to use attach tools again. As we know, to keep the problematic jvm alive, usually It's very helpful to shoot the real trouble in time.
Thanks for any reply : )
The text was updated successfully, but these errors were encountered:
hey, I' m using async-profiler when [/tmp/.java_pidXX] file is missing, that doesn't work obviously. And I found that message from stack overflow:
You cannot change the path - it is hardcoded in JVM source code. Neither you can force JVM to regenerate it, because the Attach Listener is initialized only once in HotSpot lifetime."1
https://stackoverflow.com/questions/32198820/why-jstack-not-working-when-the-tmp-java-pidnum-socket-file-has-been-deleted
So I'm thinking is there any possible way(may be a tricky/geek way) that we can recover or regenerate this file to use attach tools again. As we know, to keep the problematic jvm alive, usually It's very helpful to shoot the real trouble in time.
Thanks for any reply : )
The text was updated successfully, but these errors were encountered: