[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[eclipselink-users] dead lock
|
Hello,
Regularly, either our connection pool is fully used, or threads are
waiting for locks. Is there a locking problem in Eclipselink? We have a
big application consisting of about 20 ejb and war modules packaged in
an ear.
I wonder if this is an eclipselink bug there. We only use injected
EntityManager (only 99% sure, as there are many developers involved).
Here is part of the jstack output. Lots of threads with similar trace.
"httpSSLWorkerThread-443-121" daemon prio=3 tid=0x0000000005b21800
nid=0x271ad in Object.wait() [0xfffffd7bc78a3000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0xfffffd7c4ed21e00> (a
org.eclipse.persistence.internal.helper.ConcurrencyManager)
at java.lang.Object.wait(Object.java:485)
at
org.eclipse.persistence.internal.helper.ConcurrencyManager.acquire(ConcurrencyManager.java:93)
- locked <0xfffffd7c4ed21e00> (a
org.eclipse.persistence.internal.helper.ConcurrencyManager)
at
org.eclipse.persistence.internal.identitymaps.CacheKey.acquire(CacheKey.java:113)
at
org.eclipse.persistence.internal.identitymaps.AbstractIdentityMap.acquireLock(AbstractIdentityMap.java:107)
at
org.eclipse.persistence.internal.identitymaps.IdentityMapManager.acquireLock(IdentityMapManager.java:133)
at
org.eclipse.persistence.internal.sessions.IdentityMapAccessor.acquireLock(IdentityMapAccessor.java:92)
at
org.eclipse.persistence.internal.sessions.IdentityMapAccessor.acquireLock(IdentityMapAccessor.java:83)
at
org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:692)
begin:vcard
fn:Yannick Majoros
n:Majoros;Yannick
org:UCL;SGSI/EPC
adr;quoted-printable:;;place de l'Universit=C3=A9, 1;Louvain-la-Neuve;;1348;Belgique
email;internet:yannick.majoros@xxxxxxxxxxxx
title;quoted-printable:D=C3=A9veloppeur
tel;work:+32 10 47.94.42
tel;cell:+32 498 70.72.13
x-mozilla-html:TRUE
version:2.1
end:vcard
