-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
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
initializing deadlock issue #8712
Comments
If the problem is reproduced, could you please create a thread dump?
|
Did you manage to reproduce it? |
we use pinpoint version is v2.3.0 Among those pinpoint configuration(pinpoint.config), we set initializing log:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of pinpoint are you using?
v2.3.3
Describe the bug
I found a deadlock while initializing pintpoint version 2.3.3.
Because of this deadlock, the application system couldn't be initialized at all.
Personally I suspect two of same java constructor initializing locks may be locked each other, but not sure if this is the case, since we don't have any more details within the stack trace.
I attached the thread dump along with this.
03-17 08:13:12.012 [eadlock-monitor] WARN c.n.p.p.m.DeadlockMonitorTask -- ================================================================ [PINPOINT] Found one Java-level deadlock: If pinpoints affect the deadlock below, please put all the information posted on pinpoint's github. (https://github.com/naver/pinpoint/issues) ================================================================ "main" Id=1 BLOCKED on jdk.internal.loader.URLClassPath@4b98bcf0 owned by "Attach Listener" Id=33 at [email protected]/jdk.internal.loader.URLClassPath.getLoader(URLClassPath.java:423) - blocked on jdk.internal.loader.URLClassPath@4b98bcf0 at [email protected]/jdk.internal.loader.URLClassPath.getResource(URLClassPath.java:314) at [email protected]/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:695) at [email protected]/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:621) at [email protected]/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:579) at [email protected]/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at [email protected]/java.lang.ClassLoader.loadClass(ClassLoader.java:522) at app//org.springframework.boot.loader.jar.JarFile.getUrl(JarFile.java:321) at app//org.springframework.boot.loader.archive.JarFileArchive.getUrl(JarFileArchive.java:73) at app//org.springframework.boot.loader.Launcher.createClassLoader(Launcher.java:62) at app//org.springframework.boot.loader.Launcher.launch(Launcher.java:49) at app//org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51) "Attach Listener" Id=33 BLOCKED on [I@a131288 owned by "main" Id=1 at [email protected]/java.lang.Class.getDeclaredConstructors0(Native Method) - blocked on [I@a131288 at [email protected]/java.lang.Class.privateGetDeclaredConstructors(Class.java:3137) at [email protected]/java.lang.Class.getConstructor0(Class.java:3342) at [email protected]/java.lang.Class.newInstance(Class.java:556) at [email protected]/java.net.URL.lookupViaProperty(URL.java:1291) at [email protected]/java.net.URL.getURLStreamHandler(URL.java:1441) at [email protected]/java.net.URL.<init>(URL.java:451) at [email protected]/jdk.internal.loader.URLClassPath$JarLoader.<init>(URLClassPath.java:720) at [email protected]/jdk.internal.loader.URLClassPath$3.run(URLClassPath.java:494) at [email protected]/jdk.internal.loader.URLClassPath$3.run(URLClassPath.java:477) at [email protected]/java.security.AccessController.doPrivileged(Native Method) at [email protected]/jdk.internal.loader.URLClassPath.getLoader(URLClassPath.java:476) at [email protected]/jdk.internal.loader.URLClassPath.getLoader(URLClassPath.java:445) at [email protected]/jdk.internal.loader.URLClassPath.getResource(URLClassPath.java:314) at [email protected]/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:695) at [email protected]/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:621) at [email protected]/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:579) at [email protected]/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) at [email protected]/java.lang.ClassLoader.loadClass(ClassLoader.java:522) at [email protected]/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:431) at [email protected]/sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:535)
What did you do to trigger the bug?
This only happens on the very small chance. We've been using pinpoint v2.3.3 from this january for many instances, but this is the first and last case.
Expected behavior
pinpoint agent should be initialized without any problem.
Additional context
I feel sorry If the log wasn't helpful enough.
I would appreciate if you can guide us on how i might find better information/logs for debugging.
Thank you.
The text was updated successfully, but these errors were encountered: