]
Norman Richards closed JBSEAM-3680.
-----------------------------------
Fix Version/s: 2.0.3.CR2
Resolution: Done
Done.
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
Assignee: Norman Richards
Fix For: 2.0.3.CR2
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: