[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4388) Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state

Wed Aug 26 15:21:23 EDT 2009

    [ https://jira.jboss.org/jira/browse/JBSEAM-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12482892#action_12482892 ] 

David Thompson commented on JBSEAM-4388:
----------------------------------------

Yes, we are using JavaBean components not EJB.  Our Credentials and Identity which are scoped at SESSION actually do preserve state across restarts. If I take any of my beans and scope them at session they will survive restarts. Its only beans at the conversation context that then make things ugly. 

Sorry I don't know more about how JBoss starts up, to help troubleshoot this more. Would it help if I tried this behavior out with one of the seam examples to see if I get the same behavior?

> Components at ScopeType.CONVERSATION cause JBoss (4 & 5) to fail loading session state
> --------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4388
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4388
>             Project: Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.0.GA
>         Environment: JBoss 4.2.3 or JBoss 5.1, jboss-seam-2.2.0, JBoss set up to hot deploy.
>            Reporter: David Thompson
>            Assignee: Christian Bauer
>            Priority: Minor
>
> We currently write struts apps. One of the things we do is hot deploy these apps by setting up JBoss/Tomcat (jboss-web.deployer) to enable session persistence. This way when an app is deployed with "ant deploy", the session data can be stored out--app is torn down-- then when new app deploys the session data restores.
> If a component that is in ScopeType.CONVERSATION is instantiated and is currently in the Conversation Context when the app is deployed, then JBoss throws an error trying to reload the component and no SESSION data is restored. For example, all logged in users (data stored in Identity or Credentials) do not restore so all users get the boot. This doesn't happen if the scope on a component is EVENT or SESSION. For the way we deploy to our production system, this causes problems for us.
> The ideal solution, would be to have the conversations to come back to life, but we could also live with the conversations not being reestablished--but we really need the other session data (such as login credentials) to live through the deploy.
> AFAIK, I have looked all over the web and read the seam reference as well as Seam In Action and can't find any information about how Conversations can persist over a session (such as a redeploy this way) or over a cluster.

-- 
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