java - Object id's in jstack -
i ran deadlock in system, , here excerpts 2 jstacks taken few minutes apart
jstack 1
found 1 java-level deadlock: ============================= "com.mchange.v2.async.threadpoolasynchronousrunner$poolthread-#2": waiting lock monitor 0x00007f1ad075d2e8 (object 0x00007f1aed690ff8, com.mysql.jdbc.jdbc4resultset), held "com.mchange.v2.async.threadpoolasynchronousrunner$poolthread-#1" "com.mchange.v2.async.threadpoolasynchronousrunner$poolthread-#1": waiting lock monitor 0x00007f1ad075d390 (object 0x00007f1aed4ca6c8, com.mysql.jdbc.jdbc4connection), held "com.mchange.v2.async.threadpoolasynchronousrunner$poolthread-#2"
jstack 2
found 1 java-level deadlock: ============================= "com.mchange.v2.async.threadpoolasynchronousrunner$poolthread-#2": waiting lock monitor 0x00007f1ad075d2e8 (object 0x00007f1aec62c8a8, com.mysql.jdbc.jdbc4resultset), held "com.mchange.v2.async.threadpoolasynchronousrunner$poolthread-#1" "com.mchange.v2.async.threadpoolasynchronousrunner$poolthread-#1": waiting lock monitor 0x00007f1ad075d390 (object 0x00007f1aec6077b8, com.mysql.jdbc.jdbc4connection), held "com.mchange.v2.async.threadpoolasynchronousrunner$poolthread-#2"
in both jstacks, monitor id's same 0x00007f1ad075d2e8 , 0x00007f1ad075d390, object id's different.
there deadlock, why object id's different? shouldn't same?
Comments
Post a Comment