[
https://issues.jboss.org/browse/WELD-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596017#comment-12596017
]
Pete Muir commented on WELD-886:
--------------------------------
Yes, this didn't get fixed when Oracle contributed the shared library mode to
Weld. We should address this asap... I have no idea why the lock is static, it
should be instance based.
> AbstractContext creationLock deadlock
> -------------------------------------
>
> Key: WELD-886
> URL: https://issues.jboss.org/browse/WELD-886
> Project: Weld
> Issue Type: Bug
> Affects Versions: 1.1.1.Final
> Environment: glassfish
> Reporter: MIchail Nikolaev
> Labels: AbstractContext, applicationscoped, deadlock
>
> AbstractContext.creationLock same for all applications on same server.
> I have portlet and webservice deployed on same glassfish server.
> On start of portlet the call to managed bean (@ApplicationScoped) is occured
> (FolderService.getRootFolder). It causes to lock creationLock in
> AbstractContext, create instance for bean, then call getRootFolder as default
> postconstruct method.
> After getRootFolder calls webservice deployed on the same server. Webservice
> method access another @ApplicationScoped bean. It causes to lock creationLock
> again (in another thread) and produces deadlock.
> Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
