[
https://issues.apache.org/jira/browse/OWB-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503407#comment-14503407
]
Mark Struberg commented on OWB-1048:
------------------------------------
The context map is and will always be consistent. It doesn't make any
difference whether there is a sync cluster replication (usually at the end of
each request) or a timed async one (every 1 minute). Even if the setAttribute
did not yet get called for a request doesn't make much difference. If the user
configures async session replication then HE has to live with the behaviour.
The result will be exactly the same as if the replication would have been
triggered a few ms before the request. All the changes in the session will get
picked up on the next session replication cycle anyway. Async replication btw
strictly requires sticky session handling. So there will be no parallel updates
on different nodes in the same session.
> Store @SessionScoped beans in real HttpSession if available
> -----------------------------------------------------------
>
> Key: OWB-1048
> URL: https://issues.apache.org/jira/browse/OWB-1048
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Context and Scopes
> Affects Versions: 1.5.0
> Reporter: Mark Struberg
> Fix For: 1.5.1
>
>
> Currently we always store our @SessionScoped beans in a Map<String sessionId,
> Map<beanbags>> in memory.
> This causes some nasty issues with sessionId rewrites. We also need the
> pretty complicated FailOver handling for enabling sane cluster behaviour.
> We do not need any of those things if we utilize the real HttpSession IF
> available. That means we do still use a mem-backed Map for owb-core, but
> provide a different SessionContext impl in the owb-web module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
