[
http://jira.jboss.com/jira/browse/JBAOP-360?page=all ]
Flavia Rainone closed JBAOP-360.
--------------------------------
Resolution: Done
I wrote a test that should simulate the same described situation, but I didn't manage
to reproduce the bug,
Despite that, now the initialization of class advisors is synchronized with configuration
operations (like addBinding), which solves the described problem.
DeadLock when multiple threads are loading aspects
--------------------------------------------------
Key: JBAOP-360
URL:
http://jira.jboss.com/jira/browse/JBAOP-360
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.5.0.GA, 1.5.1.GA, 1.5.2.GA, 1.5.3.GA
Reporter: Clebert Suconic
Assigned To: Flavia Rainone
Fix For: 1.5.4.GA, 2.0.0.alpha3
When multiple threads are loading aspect there is a possibility of a dead lock, of locks
boucing between a WeakHashMap lock and ClassAdvisor.
You will need a multiple thread test loading Aspects simultaneously.
Tim Fox has found this as part of JBMESSAGING-797
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira