8 Replies Latest reply on May 10, 2007 8:29 AM by nctrax

    Seam remoting conversation - possible problem?

    chris.morrisette

      I am still having problems with Seam Remoting, within a conversation the state of a SFSB is lost. I had isolated some cases to being because my application restarted and not restarting the browsers session, but have found other unrelated cases.

      I was able to capture the log of an instance of this happening. The conversation id is '6' and the SFSB (with a scope of 'conversation') is 'ServiceBusiness'.

      At time datestamp '2006-12-19 12:20:33,656' you can see that seam conversation 6 is invoking a method on ServiceBusiness instance ServiceBusinessImpl@9403b0.

      At time datestamp '2006-12-19 12:20:37,750' you can see that seam conversation 6 instantiates a new ServiceBusiness object and invokes a method on ServiceBusiness instance ServiceBusinessImpl@b73feb.

      You can see that earlier invocations of conversation 6 all operate on ServiceBusinessImpl@9403b0.

      In looking at the log, the only thing that pops out at me is that Conversation id '2' times out at time datestamp 2006-12-19 12:20:36,468, but this shouldn't have any impact on conversation 6, should it?

      Am I doing something wrong?

      I am about to jump into the source, but wanted to see if anybody had any suggestions first.

      Thanks for any help,
      Chris

      jboss-4.0.5.GA
      Seam 1.1.0.GA
      jdk1.5.0_09

      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Lifecycle] >>> Begin web request
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.manager
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.manager
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.manager
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.core.Manager] No stored conversation, or concurrent call to the stored conversation
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] instantiating Seam component: serviceBusiness
      2006-12-19 12:20:25,453 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-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] initializing new instance of: serviceBusiness
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] done initializing: serviceBusiness
      2006-12-19 12:20:25,453 DEBUG [org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor] ++++ LongLivedSessionPropagationInterceptor
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.interpolator
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.interpolator
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.interpolator
      2006-12-19 12:20:25,453 ERROR [com.zua.business.ServiceBusinessImpl] Instantiating Service Business object: com.zua.business.ServiceBusinessImpl@9403b0
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.core.Manager] Beginning long-running conversation
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.conversation
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.conversation
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.conversation
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.core.Manager] Storing conversation state: 6
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Lifecycle] After request, destroying contexts
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying business process context
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing server-side conversation context
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing session context
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying event context
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.manager
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web request
      2006-12-19 12:20:25,453 DEBUG [org.jboss.seam.remoting.ExecutionHandler] ended request
      2006-12-19 12:20:25,453 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-12-19 12:20:25,453 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:25,593 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-12-19 12:20:25,593 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:25,593 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-12-19 12:20:25,593 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:25,609 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-12-19 12:20:25,609 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:25,625 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-12-19 12:20:25,625 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:25,656 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-12-19 12:20:25,656 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Lifecycle] >>> Begin web request
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.manager
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.manager
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.manager
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.core.Manager] Restoring conversation with id: 6
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: serviceBusiness
      2006-12-19 12:20:25,734 DEBUG [org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor] ++++ LongLivedSessionPropagationInterceptor
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.interpolator
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.interpolator
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.interpolator
      2006-12-19 12:20:25,734 ERROR [com.zua.business.ServiceBusinessImpl] Executing method on Service Business: com.zua.business.ServiceBusinessImpl@9403b0
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.core.Manager] Storing conversation state: 6
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Lifecycle] After request, destroying contexts
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying business process context
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing server-side conversation context
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing session context
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying event context
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.manager
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web request
      2006-12-19 12:20:25,734 DEBUG [org.jboss.seam.remoting.ExecutionHandler] ended request
      2006-12-19 12:20:25,734 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-12-19 12:20:25,734 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.contexts.Lifecycle] >>> Begin web request
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.manager
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.manager
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.manager
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.core.Manager] Restoring conversation with id: 6
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: serviceBusiness
      2006-12-19 12:20:28,187 DEBUG [org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor] ++++ LongLivedSessionPropagationInterceptor
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.interpolator
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.interpolator
      2006-12-19 12:20:28,187 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.interpolator
      2006-12-19 12:20:28,187 ERROR [com.zua.business.ServiceBusinessImpl] Executing method on Service Business: com.zua.business.ServiceBusinessImpl@9403b0
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:28,203 DEBUG [org.jboss.ejb3.entity.ManagedEntityManagerFactory] ************** closing entity managersession **************
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.core.Manager] Storing conversation state: 6
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.contexts.Lifecycle] After request, destroying contexts
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying business process context
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing server-side conversation context
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing session context
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying event context
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.manager
      2006-12-19 12:20:28,203 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web request
      2006-12-19 12:20:28,250 DEBUG [org.jboss.seam.remoting.ExecutionHandler] ended request
      2006-12-19 12:20:28,250 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-12-19 12:20:28,250 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.contexts.Lifecycle] >>> Begin web request
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.manager
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.manager
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.manager
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.core.Manager] Restoring conversation with id: 6
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: serviceBusiness
      2006-12-19 12:20:33,656 DEBUG [org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor] ++++ LongLivedSessionPropagationInterceptor
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.interpolator
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.interpolator
      2006-12-19 12:20:33,656 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.interpolator
      2006-12-19 12:20:33,656 ERROR [com.zua.business.ServiceBusinessImpl] Executing method on Service Business: com.zua.business.ServiceBusinessImpl@9403b0
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:36,468 DEBUG [org.jboss.ejb3.entity.ManagedEntityManagerFactory] ************** closing entity managersession **************
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.core.Manager] Storing conversation state: 6
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.core.Manager] conversation timeout for conversation: 2
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.conversation
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Contexts] destroying: serviceBusiness
      2006-12-19 12:20:36,468 DEBUG [org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor] ++++ LongLivedSessionPropagationInterceptor
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.interpolator
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.interpolator
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.interpolator
      2006-12-19 12:20:36,468 ERROR [com.zua.business.ServiceBusinessImpl] Destroying Service Business object: com.zua.business.ServiceBusinessImpl@1aaf3cb
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.interceptors.RemoveInterceptor] Stateful component was removed: serviceBusiness
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Lifecycle] After request, destroying contexts
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying business process context
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing server-side conversation context
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing session context
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying event context
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.manager
      2006-12-19 12:20:36,468 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web request
      2006-12-19 12:20:36,500 DEBUG [org.jboss.seam.remoting.ExecutionHandler] ended request
      2006-12-19 12:20:36,500 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-12-19 12:20:36,500 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:36,531 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-12-19 12:20:36,531 DEBUG [org.jboss.seam.servlet.SeamExceptionFilter] ended request
      2006-12-19 12:20:37,734 DEBUG [org.jboss.seam.contexts.Lifecycle] >>> Begin web request
      2006-12-19 12:20:37,734 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.manager
      2006-12-19 12:20:37,734 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.manager
      2006-12-19 12:20:37,750 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.manager
      2006-12-19 12:20:37,750 DEBUG [org.jboss.seam.core.Manager] Restoring conversation with id: 6
      2006-12-19 12:20:37,750 DEBUG [org.jboss.seam.Component] instantiating Seam component: serviceBusiness
      2006-12-19 12:20:37,750 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-12-19 12:20:37,750 DEBUG [org.jboss.seam.Component] initializing new instance of: serviceBusiness
      2006-12-19 12:20:37,750 DEBUG [org.jboss.seam.Component] done initializing: serviceBusiness
      2006-12-19 12:20:37,750 DEBUG [org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor] ++++ LongLivedSessionPropagationInterceptor
      2006-12-19 12:20:37,750 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.interpolator
      2006-12-19 12:20:37,750 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.interpolator
      2006-12-19 12:20:37,750 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.interpolator
      2006-12-19 12:20:37,750 ERROR [com.zua.business.ServiceBusinessImpl] Executing method on Service Business: com.zua.business.ServiceBusinessImpl@b73feb
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: org.jboss.seam.core.persistenceContexts
      2006-12-19 12:20:37,781 DEBUG [org.jboss.ejb3.entity.ManagedEntityManagerFactory] ************** closing entity managersession **************
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.core.Manager] Storing conversation state: 6
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.contexts.Lifecycle] After request, destroying contexts
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying business process context
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing server-side conversation context
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing session context
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying event context
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.manager
      2006-12-19 12:20:37,781 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web request


        • 1. Think I found the problem
          chris.morrisette

          Ok. I think I found the problem in the class:
          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.

          Thoughts? Am I completely wrong?

          Thanks

          • 2. Re: Seam remoting conversation - possible problem?
            chris.morrisette

            Just some more clarification. The method that is cleaning up timed out conversations is:

            org.jboss.seam.core.Manager.endRequest(ContextAdaptor session)

            Specifically the line: Manager.instance().conversationTimeout(session);

            Line number 347

            • 3. Re: Seam remoting conversation - possible problem?
              gavin.king

              Whoah! That looks like a *really* bad bug....please add a JIRA issue, priority "Blocker".

              • 4. Re: Seam remoting conversation - possible problem?
                chris.morrisette

                Thanks for the quick response.

                Created Jira 618

                http://jira.jboss.org/jira/browse/JBSEAM-618

                • 5. Re: Seam remoting conversation - possible problem?
                  gavin.king

                  OK, I just committed a fix. Please test it for me. thanks.

                  • 6. Re: Seam remoting conversation - possible problem?
                    gavin.king

                    BTW, congratulations, that was the first serious bug found in 1.1 GA!

                    • 7. Re: Seam remoting conversation - possible problem?

                      I have the same error in the version 1.2.1GA. Is this me or is this due to an error of versionning :

                      ""
                      I currently study JBoss Seam 1.2.1GA in order to use it soon for an application in production.

                      I created a conversation based on a pageflow. The conversation proceeds perfectly. I can start and use at the same time several instance of this conversation by using the functionality of workspace management.

                      Here's my problem:

                      When I switch from one conversation to another, all functions well.
                      However, when I finish one of the conversations, the second pageflow does not function any more (I can only destroy it thanks to the workspace manager).

                      I tried to use different manner of starting and finishing the conversation (via a page or an action). I thought that that could be with a mechanism of hierarchy of the conversations but when I added nested=false to the @Begin, nothing changed.

                      I like the framework much and I would like to use it for a customer.

                      I thank you very much for any help !
                      ""

                      • 8. Re: Seam remoting conversation - possible problem?

                        Ok, I just saw JIRA-618 (version 1.1.0) and JIRA-1112 (version 1.3.0.BETA1).

                        Sorry for this new post about the same problem !
                        Can you tell when do you plan to fix this bug ?