Hi,


We currently have Spring running within a jboss container. We have had this configuration for some time, and recently upgraded to Spring 3 and to the latest java 6 patch 20.

Ever since then, after running for a couple of hours, we encounter a deadlock. It is difficult to pinpoint exactly what the issue is, but we think it may linked to the spring 3 upgrade.

We do compile time weaving with @Configurable in most cases.

Here are the deadlocks we have seen :

Thread: WorkManager(2)-85 : priority:5, demon:true, threadId:536, threadState:BLOCKED, lockName:java.lang.Class@2d015ad1
java.lang.Class.initAnnotationsIfNecessary(Class.j ava:3067)
java.lang.Class.getAnnotation(Class.java:3029)
java.lang.Class.isAnnotationPresent(Class.java:304 2)
qut.common.delegate.PositionManagerDelegate.(Posit ionManagerDelegate.java:18)

Thread: WorkManager(2)-38 : priority:5, demon:true, threadId:479, threadState:BLOCKED, lockName:java.lang.Class@741b31f2
java.lang.Class.initAnnotationsIfNecessary(Class.j ava:3067)
java.lang.Class.getAnnotation(Class.java:3029)
org.jboss.aop.annotation.AnnotationElement.getVisi bleAnnotation(AnnotationElement.java:88)
org.jboss.aop.Advisor.resolveAnnotation(Advisor.ja va:321)

Thread: AsyncNotifier-401 : priority:5, demon:false, threadId:812, threadState:BLOCKED, lockName:java.lang.Class@741b31f2
java.lang.Class.initAnnotationsIfNecessary(Class.j ava:3067)
java.lang.Class.getAnnotation(Class.java:3029)
org.jboss.aop.annotation.AnnotationElement.getVisi bleAnnotation(AnnotationElement.java:88)
org.jboss.aop.Advisor.resolveAnnotation(Advisor.ja va:321)

There is nothing in the stack trace relating to spring, but I am not sure if the injections/annotations resolutions would show in the stack trace.

Any suggestions would be greatly appreciated.

Thanks
Daniel