[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468125#comment-13468125
]
Michael Freedman commented on PORTLETBRIDGE-231:
------------------------------------------------
Fixed in the Oracle branch by having the thread holding the lock merely push
the scope being removed onto a queue and then notifies waiting threads. A
single (app wide) thread listens/waits to be notified this queue has entries
and when its woken up, takes the scope object from the queue and executes the
predestroy logic.
> Request Threads can get stuck when Bridge removes a scope
> ---------------------------------------------------------
>
> Key: PORTLETBRIDGE-231
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-231
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Affects Versions: 1.0.0, 2.0.0, 3.0.0
> Reporter: Michael Freedman
> Assignee: Michael Freedman
>
> During the process of removing the scopes associated with a given session
> when a session is invalidated/released, request threads can become stuck
> waiting on the scope manager lock because action of iterating over all the
> objects (and their methods) in the scope to find and then call managed bean
> predestroy methods occurs while the lock is held.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
