[
https://issues.apache.org/jira/browse/OWB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004536#comment-13004536
]
Joe Bergmark commented on OWB-523:
----------------------------------
Thanks for catching my typo with the null check, I"ll fix that today.
As far as the same instance of SessionUser being used during "normal"
operation. This might be due to the internal map that OWB has of
SessionContexts. We are going to find the SessionContext in that map in the
SessionManager if the server hasn't been stopped or that Session hasn't been
destroyed. (callback to HttpSessionListener sessionDestroyed).
In the case of restarting tomcat, the map is going to be empty, so presumably
we are deserializing the @SessionScoped bean to restore the data.
Do you see the value restored after tomcat is restarted?
> @SessionScoped bean failover does not work
> ------------------------------------------
>
> Key: OWB-523
> URL: https://issues.apache.org/jira/browse/OWB-523
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Environment: MyFaces 2.0.3, OWB 1.0.0, Tomcat 7.0.8,
> memcached-session-manager
> Reporter: Thomas Andraschko
> Assignee: Joe Bergmark
> Priority: Minor
>
> OWB failover for @SessionScoped beans does not work.
> A detailed description and a sample project can be found here:
> https://github.com/magro/msm-sample-webapp/tree/openwebbeans
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
