[jboss-jira] [JBoss JIRA] Closed: (JBCLUSTER-221) DistributableSession should not expose Atomic objects for version and timestamp

Tue Apr 14 13:49:36 EDT 2009

     [ https://jira.jboss.org/jira/browse/JBCLUSTER-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry closed JBCLUSTER-221.
--------------------------------------

    Resolution: Done


> DistributableSession should not expose Atomic objects for version and timestamp
> -------------------------------------------------------------------------------
>
>                 Key: JBCLUSTER-221
>                 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-221
>             Project: JBoss Clustering
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: HA-Server-Cache-JBC, HA-Server-Cache-SPI
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: HA-Server-Cache-SPI 2.0.0.GA, HA-Server-Cache-JBC 2.0.0.GA
>
>
> The fact that a DistributedSession impl maintains its version and timestamp in an AtomicInteger and AtomicLong should not be in the SPI.
> Besides the basic design issue, goal is to prevent replication of those objects by ha-server-cache-jbc , which requires a memory fence on remote nodes when deserialized, even if the replicated session is never accessed.

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