pamr and javassist deadlock

[activeeon-bot]

Original issue created by Salageanu Emil on 18, Aug 2014 at 15:13 PM - PALIGHT-68

---

A scheduler client runs inside a Tomcat (TEFIS pacagrid connector). Client code is here: https://scm.gforge.inria.fr/svn/tefis/trunk/connectors/pacagrid-connector\

We have this deadlock at startup: JNI global references: 1533

Found one Java-level deadlock:

"State Updater Thread": waiting to lock monitor 0x00007f7615812610 (object 0x00000000ccd9a5d0, a javassist.ClassPool), which is held by "ProActive PAMR message handler #2-thread-1" "ProActive PAMR message handler #2-thread-1": waiting to lock monitor 0x00007f7618011b00 (object 0x00000000cc9f5810, a org.objectweb.proactive.core.mop.MOPClassLoader), which is held by "State Updater Thread"

Java stack information for the threads listed above:

"State Updater Thread": at javassist.ClassPool.get0(ClassPool.java:451)

• waiting to lock <0x00000000ccd9a5d0> (a javassist.ClassPool) at javassist.ClassPool.get(ClassPool.java:433) at org.objectweb.proactive.core.mop.JavassistByteCodeStubBuilder.create(JavassistByteCodeStubBuilder.java:142) at org.objectweb.proactive.core.mop.MOPClassLoader.loadClass(MOPClassLoader.java:243)
• locked <0x00000000cc9f5810> (a org.objectweb.proactive.core.mop.MOPClassLoader) at org.objectweb.proactive.core.mop.MOPClassLoader.loadClass(MOPClassLoader.java:171) at org.objectweb.proactive.core.mop.MOP.createStubClass(MOP.java:606) at org.objectweb.proactive.core.mop.MOP.findStubConstructor(MOP.java:645) at org.objectweb.proactive.core.mop.MOP.createStubObject(MOP.java:815) at org.objectweb.proactive.core.mop.MOP.newInstance(MOP.java:331) at org.objectweb.proactive.core.mop.MOP.newInstance(MOP.java:189) at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.reifyAsAsynchronous(AbstractBodyProxy.java:226) at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.invokeOnBody(AbstractBodyProxy.java:143) at org.objectweb.proactive.core.body.proxy.AbstractBodyProxy.reify(AbstractBodyProxy.java:114) at pa.stub.org.ow2.proactive.scheduler.common.util._StubCachingSchedulerProxyUserInterface.getRevisionVersionAndSchedulerState(_StubCachingSchedulerProxyUserInterface.java) at org.tefis.connector.pacagrid.tciexec.SchedulerStateCaching$2.run(SchedulerStateCaching.java:155) at java.lang.Thread.run(Thread.java:636) "ProActive PAMR message handler #2-thread-1": at org.objectweb.proactive.core.mop.MOPClassLoader.loadClass(MOPClassLoader.java:176)
• waiting to lock <0x00000000cc9f5810> (a org.objectweb.proactive.core.mop.MOPClassLoader) at org.objectweb.proactive.core.mop.MOPClassLoader.loadClass(MOPClassLoader.java:162) at org.objectweb.proactive.core.mop.MOPClassLoader.getClassData(MOPClassLoader.java:91) at org.objectweb.proactive.core.mop.MOPClassLoader.getResource(MOPClassLoader.java:319) at javassist.LoaderClassPath.find(LoaderClassPath.java:86) at javassist.ClassPoolTail.find(ClassPoolTail.java:369)

[activeeon-bot]

Original comment posted by Laurent Pellegrino on 24, Feb 2015 at 11:27 AM

---

Does someone know what is the login and password to use in order to access the link from the the description?

[activeeon-bot]

Original comment posted by Laurent Pellegrino on 24, Feb 2015 at 16:10 PM

---

Iyad has tried with his credentials but it does not work. They are probably project specific. However, according to the stacktrace, the bug should be fixed by the patch I have proposed for PALIGHT-46.