[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4669) Major java deadlock between BijectionInterceptor and Component since the getInstanceFromFactory method is synchronized
[
https://jira.jboss.org/browse/JBSEAM-4669?page=com.atlassian.jira.plugin....
]
Denis Forveille commented on JBSEAM-4669:
-----------------------------------------
I will remove the synchronized keyword on the problematic method as the side effects are
desastrous...
As a consequence, JBSEAM-2419 should re-appear
In the meantime, maybe people should use the workaround described in JBSEAM-2419, ie add
the "synchronized" keyword for all methods annotated with "@Unwrap"
Major java deadlock between BijectionInterceptor and Component since
the getInstanceFromFactory method is synchronized
-----------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-4669
URL: https://jira.jboss.org/browse/JBSEAM-4669
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.1.CR2
Reporter: Denis Forveille
Assignee: Denis Forveille
Priority: Blocker
Fix For: 2.2.1.CR2
To address JBSEAM-2419, the Component.getInstanceFromFactory(String name) is now
"synchronized"
This causes java deadlocks under stress with the call to lock.lock() in
BinjectionInterceptor ...
For us our apps freezes after 10 minutes in production,,,
I don't know why this method has been marked as synchronized but this is the cause of
the deadlock...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira