[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3680) Locking issue for ConversationEntry when redirecting at ExceptionFilter

Takayoshi Kimura (JIRA) jira-events at lists.jboss.org
Fri Nov 14 04:21:36 EST 2008

    [ https://jira.jboss.org/jira/browse/JBSEAM-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12438431#action_12438431 ] 

Takayoshi Kimura commented on JBSEAM-3680:

Normally redirection between the pages go through keep alive connection and those requests are processed in a same thread. However in some cases, such like keep-alive off or using html frame, this problem will appear.

> Locking issue for ConversationEntry when redirecting at ExceptionFilter
> -----------------------------------------------------------------------
>                 Key: JBSEAM-3680
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3680
>             Project: Seam
>          Issue Type: Bug
>          Components: Exception Handling
>    Affects Versions: 2.0.2.SP1
>         Environment: Windows XP SP2, JBoss EAP 4.3
>            Reporter: Hiroyuki Wada
>            Priority: Critical
>         Attachments: test-JBSEAM-3680.diff
> When redirecting at ExceptionFilter, it seems that the ConversationEntry lock is not released.
> Therefore, if next request is processed by the another thread, the thread wait for until unlocking.
> This results in the user being redirected to the no-conversation-view-id after the concurrent-request-timeout expires.
> I checked the Seam 2.0.2.SP1 source. It seems that the unlocking process for ConversationEntry
> is skipped when Exception is thrown from JSF Action that invoked in INVOKE_APPLICATION phase.
> When Exception is not thrown, the lock is release after INVOKE_APPLICATION phase.
> (at method calling "afterResponseComplete(facesContext)" at 249 line of SeamPhaseListener.java)
> When Exception is thrown, this method is not called because of the result of FacesContext#getResponseComplete()
> is FALSE.

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


More information about the seam-issues mailing list