[jboss-jira] [JBoss JIRA] (AS7-6946) Redesign web session clustering

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768585#comment-12768585 ] 

Brian Stansberry commented on AS7-6946:
---------------------------------------

Sounds good.

Alpha1 is scheduled for May 6. Please reschedule. :)
                
> Redesign web session clustering
> -------------------------------
>
>                 Key: AS7-6946
>                 URL: https://issues.jboss.org/browse/AS7-6946
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Clustering
>    Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>             Fix For: 8.0.0.Alpha1
>
>
> The current web session replication code has been around for ages and suffers from a number of issues:
> * By maintaining a separate local map of sessions in conjunction with the session data stored in the distributed cache, stale data is inevitable - an number of issues have cropped up in EAP testing.
> * Extra concurrency measures are required to ensure synchronicity of the local session map with the distributed cache.
> * Extra logic/locking is required to invalidate the local session map is required per request
> * AtomicMaps, on which the currently implementation relies, have proven buggy
> * Session access outside of the scope of the replication valve is possible and problematic
> * Maintaining sessions locally means that the clustering code needs to implement passivation and expiration manually - instead of leveraging Infinispan full capabilities.
> * The current code base is tightly coupled to JBoss Web.  Migrating the code to support Undertow will inevitably introduce issues and code duplication.
> The new design will incorporate a proper SPI for the servlet container.  Thus the logic to integrate with Undertow vs JBoss Web will be relatively thin.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira