[seam-dev] Re: Blocked threads

[Christian Bauer]

On Jun 05, 2008, at 10:41 , Christian Bauer wrote:

> During load spikes in production I find plenty of BLOCKED threads  
> with this stack:

Slightly different picture now, all BLOCKED threads have this stack:

sun.reflect.annotation.AnnotationType.getInstance(AnnotationType.java: 
63)
sun 
.reflect 
.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:202)
sun 
.reflect 
.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:69)
sun 
.reflect 
.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:52)
java.lang.reflect.Field.declaredAnnotations(Field.java:1002)
java.lang.reflect.Field.getAnnotation(Field.java:989)
java 
.lang 
.reflect.AccessibleObject.isAnnotationPresent(AccessibleObject.java:175)
org 
.jboss 
.seam 
.persistence 
.ManagedEntityIdentityInterceptor 
.ignore(ManagedEntityIdentityInterceptor.java:155)
org 
.jboss 
.seam 
.persistence 
.ManagedEntityIdentityInterceptor 
.entityIdsToRefs(ManagedEntityIdentityInterceptor.java:120)
org 
.jboss 
.seam 
.persistence 
.ManagedEntityIdentityInterceptor 
.aroundInvoke(ManagedEntityIdentityInterceptor.java:46)
org 
.jboss 
.seam 
.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org 
.jboss 
.seam 
.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java: 
31)
org 
.jboss 
.seam 
.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org 
.jboss 
.seam 
.core 
.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42)
org 
.jboss 
.seam 
.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java: 
107)
org 
.jboss 
.seam 
.intercept 
.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166)
org 
.jboss 
.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102)
org.jboss.seam.wiki.core.dao.WikiManagedPersistenceContext_$ 
$_javassist_9.getEntityManager(WikiManagedPersistenceContext_$ 
$_javassist_9.java)

Still, everything points to ManagedEntityIdentityInterceptor as the  
culprit.