Does this happen when you run standalone? I have had some weird issues with
debugging in Eclipse 3.2.0 (3.2.1 seems better).
A sample application would really be appreciated, I am very keen to get this
problem fixed.
View the original post :
i would say that we have a deadlock issue when one thread is using jbossaop
classloader and another is using the default one ( eg not the jbossaop
classloader). if all threads are using the jbossaop classloader we shouldnt see
this error (i hope).
i havent had the time to look more deeply into
hm, its seems like we got a general concurrent bug here. i was hoping it was
only generated advisors (SuperClassesFirstWeavingStrategy) that caused the
problem...
i looks like our systemclassloader is creating a deadlock, if you got the time.
could you try to deploy the app in jboss and see if
Here are the stack traces of the locked threads (copied from Eclipse's
debugger, after suspending them):
Thread 1
Thread [TotalRecordings Thread] (Suspended)
ClassLoader.findBootstrapClass(String) line: not available [native
method]
hm, its quite possible that we have several concurrent issues with the
generated advisors instrumentation that uses SuperClassesFirstWeavingStrategy.
you can easily tell jboss aop to use a different instrumentor (its only from
jboss aop 2.0 that generated advisors are default instrumentor).
add
Thank you very much for your help!
I've tried using ClassicWeavingStrategy. Unfortunately, the problem still
occurs: One thread is stuck as before (ClassLoader.findBoostrapClass(...) ) and
the other is now stuck on ClassicWeavingStrategy.translate(AspectManager,
String, ClassLoader, byte[]) -
Hi again,
I've not been able to recreate the bug in a test program. However, it now
definitely happens again, with the updated lib. One thread is stuck on
ClassLoader.findBoostrapClass() and another one on
SuperClassesFirstWeavingStrategy.obtainCtClassInfo(). One of them is trying to
load an
Thanks for your quick reply (and for a great product :-) ) !
I tried out the fix, and it seems to be working. However, trying a few runs,
one of them still seemed to hang as before. This didn't happen again, though...
I'm trying to create a simple program to reproduce the bug (using the old
hi, thanks for the feedback. SuperClassesFirstWeavingStrategy is used with the
generated advisors instrumentation. it is very different from the other weaving
types and as you can see, we havent fully tested it yet.
i have commited a quickfix to the problem (i hope) in svn. if you could try it
