It seems I'm doing something completely wrong. I discovered that the stateful session conversation context bean is created several times during rendering of the single request. Here the debug output: This is the first attempt to access the Seam Component named "leistungsschein". It isn't there, it is created, everything is fine. | 2006-07-20 15:14:32,177 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: leistungsschein | 2006-07-20 15:14:32,177 DEBUG [org.jboss.seam.Component] instantiating Seam component: leistungsschein | 2006-07-20 15:14:32,177 DEBUG [org.jboss.seam.util.Naming] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} | 2006-07-20 15:14:32,177 DEBUG [org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor] ++++ LongLivedSessionPropagationInterceptor | Afterwards, lots of successful lookups like this: | 2006-07-20 15:14:33,224 DEBUG [org.jboss.seam.jsf.SeamVariableResolver] resolving name: leistungsschein | 2006-07-20 15:14:33,224 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: leistungsschein | This all takes place during RENDER_RESPONSE and matches the EL calls to the Seam component in the page. But then, suddenly: | 2006-07-20 15:14:33,912 DEBUG [org.jboss.seam.interceptors.RemoveInterceptor] Stateful component was removed: leistungsschein | Seam intercepts that the container has decided to remove the bean. What follows is clear - Seam recreates the bean, runs into @Begin method and complains about the already begun conversation. But why does the container decide to remove the stateful bean?? I fear that it's an absolute beginner's error. But, in fact, I am an absolute beginner. Hope it's allowed to make some. Regards, Marcus. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959563#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...