[
https://jira.jboss.org/browse/JBSEAM-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12536802#action_12536802
]
Ondrej Skutka commented on JBSEAM-4669:
---------------------------------------
Strange. We have stress-tested Seam booking after the JBSEAM-2419 patch and it
worked fine. And it didn't work before the patch. Does
ConcurrentFactoryTest pass?
Maybe the deadlock bug is caused with something else. Can you reproduce it? Do
you have a test for it?
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
