Conversation deadlock for seam wicket pages with multiple request targets ------------------------------------------------------------------------- Key: JBSEAM-4062 URL: https://jira.jboss.org/jira/browse/JBSEAM-4062 Project: Seam Issue Type: Bug Components: Wicket Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 2.2.0.CR1 If onRequestTarget is called multiple times in a given request thread, Manager.restoreConversation() will be called twice, and that class does not defend against this by making the second call a no-op, but instead increments the lock count on the conversation blindly, so when the request returns the conversation will be erroneously left with a lock count of one, and can't be subsequently used. -- 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