]
Ales Justin commented on WELD-865:
----------------------------------
I'm now throwing BusyConversationException.
I'll think about the XXX and other things we need to handle.
Weld allows for concurrent call to conversation
-----------------------------------------------
Key: WELD-865
URL:
https://issues.jboss.org/browse/WELD-865
Project: Weld
Issue Type: Bug
Components: Scopes & Contexts, Web Tier integration (JSF, JSP, EL and
Servlet)
Affects Versions: 1.1.0.Final
Reporter: George Sapountzis
Assignee: Ales Justin
Fix For: 1.2.0.Beta1
Concurrent calls to a @ConversationScoped component:
Thread 1:
AbstractConversationContext.activate(String cid)
ConversationImpl.lock(long timeout) <-- returns true
correctly proceed inside method
Thread 2:
AbstractConversationContext.activate(String cid)
ConversationImpl.lock(long timeout) <-- returns false but activate() does not check
result !!!
*incorrectly* proceed inside method
----
I think AbstractConversationContext.activate(String cid) should check the result of
ConversationImpl.lock(long timeout) and not allow the second thread to proceed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: