[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-618) Removing conversation components from current thread instead of timed-out thread

Removing conversation components from current thread instead of timed-out thread -------------------------------------------------------------------------------- Key: JBSEAM-618 URL: http://jira.jboss.com/jira/browse/JBSEAM-618 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.1.0.GA Environment: jboss-4.0.5.GA Seam 1.1.0.GA jdk1.5.0_09 Reporter: Chris Morrisette Assigned To: Gavin King Priority: Blocker Fix For: 1.1.1.GA org.jboss.seam.interceptors.RemoveInterceptor The line (77): getComponent().getScope().getContext().remove( getComponent().getName() ); Will remove a bean with the specified name from the conversation associated with the current thread. The problem is, that the current thread is cleaning up timed out conversations not associated with the current thread. Since, getComponent().getScope().getContext().remove( getComponent().getName() ); removes objects from the current thread (instead of the timed out thread) you end up having objects removed from the current threads conversation by accident. I was also able to watch this happen in the Seam.debug servlet. Starting two conversations a minute after each other with the same Components loaded, and the component would be removed from the conversation associated with the current thread, not the thread that is timing out.