[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2926) CLONE -Locking issue for ConversationEntry when using Conversation.instance().leave()

[Tomas Cerny (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2926?page=comments#action_12410645 ] 
            
Tomas Cerny commented on JBSEAM-2926:
-------------------------------------

patch from Jacob is supposed to be 

public void leaveConversation()
 {
+      unlockConversation();
       initializeTemporaryConversation();
}

> CLONE -Locking issue for ConversationEntry when using Conversation.instance().leave()
> -------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-2926
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2926
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.1.GA
>            Reporter: Tomas Cerny
>         Assigned To: Pete Muir
>            Priority: Minor
>             Fix For: 2.1.0.BETA1, 2.0.2.CR1
>
>
> When using Conversation.instance().leave(), it seems that the ConversationEntry lock is not released.  *Sometimes* it can be obtained when attempting to resume the conversation but other times it cannot.  This results in the user being redirected to the no-conversation-view-id after the concurrent-request-timeout expires.
> This can be observed by placing Conversation.instance.leave() in an action that redirects to another page.  Then simply use the back-button and resume the conversation by clicking a link on the page.  You may have to try this several times to get the result.  I will see if I can create a reliable test case and attach it.
> Manager.switchConversation() performs an unlock of the ConversationEntry prior to switching, which would also make sense in the case of leave (since it is really a switch to a temp conversation).
> The workaround is simply executing the following:
> Code:
> Conversation conversation = Conversation.instance();
>         
> ConversationEntry entry = 
>             ConversationEntries.instance().getConversationEntry(conversation.getId());
> conversation.leave();
> entry.unlock();

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira