[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4480) Sometimes JSF lifecycle not completing which leaves conversation in locked state causing concurrent conversation error

Sometimes JSF lifecycle not completing which leaves conversation in locked state causing concurrent conversation error ---------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4480 URL: https://jira.jboss.org/jira/browse/JBSEAM-4480 Project: Seam Issue Type: Bug Components: Core, JSF Integration Affects Versions: 2.2.0.GA Environment: Linux Reporter: Ross Mills Attachments: concurrent-conv-err.log I have an Seam app that has a left menu on every page. When the user selects an item from the menu, it ends the current conversation and starts a new one. However, once in a while, I get a concurrent conversation exception. I have an automated test that does the following: (1) Logs the user in. (2) 10 seconds later, the user selects an item from the left hand menu (which ends the current conversation and begins a new one). This causes a seach form to appear. (3) 10 seconds later, the user fills in the form and submits. The search results are displayed. (4) 10 seconds later, the user navigates through the search results and drills down. (5) 10 seconds later, the user returns to step (2) by selecting the same item from the left hand menu and repeats the above steps. The user is able to cycle through these steps anywhere from a few seconds to several minutes until the concurrent conversation error occurs. When the error occurs, it is when the user attempts to submit the search form. The logs indicate that when the search form is displayed, the JSF lifecycle is not progressing beyond the RESTORE_VIEW phase. This causes the conversation to remain locked. Then when the user attempts to submit the form, the new thread finds the conversation locked and generated the concurrent conversation exception. My company policy may not allow me to provide you with code that you can use to duplicate the problem. But snippets of the logs can be found in the JBoss forum reference I am including.