[JBoss JIRA] Closed: (JBCLUSTER-14) http session failover using single shared DB with cache loader
by Brian Stansberry (JIRA)
[ https://jira.jboss.org/jira/browse/JBCLUSTER-14?page=com.atlassian.jira.p... ]
Brian Stansberry closed JBCLUSTER-14.
-------------------------------------
Fix Version/s: (was: Backlog)
Resolution: Out of Date
This was done for EAP 5.0 and AS 6.0.0.M1.
> http session failover using single shared DB with cache loader
> --------------------------------------------------------------
>
> Key: JBCLUSTER-14
> URL: https://jira.jboss.org/jira/browse/JBCLUSTER-14
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Web Tier
> Reporter: Ben Wang
> Assignee: Brian Stansberry
> Priority: Minor
> Original Estimate: 8 weeks
> Remaining Estimate: 8 weeks
>
> To achieve http session failover, alternatively we can use a single shared DB with CacheLoader for multiple cache instances. All the session states will be persisted to the shared DB. When failing over, it will simply retrieve from the DB if it is not there yet.
> This approach can scale very well. But it will be slower since every session setAttribute operation involves trip to DB. JBossCache already supports this semantics now. All we need is someone to verify it and benchmark it.
--
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
14 years, 9 months
[JBoss JIRA] Created: (EJBTHREE-2053) Infinispan replication configuration via @CacheConfig
by Brian Stansberry (JIRA)
Infinispan replication configuration via @CacheConfig
-----------------------------------------------------
Key: EJBTHREE-2053
URL: https://jira.jboss.org/jira/browse/EJBTHREE-2053
Project: EJB 3.0
Issue Type: Feature Request
Components: cache, Clustering
Reporter: Brian Stansberry
Make the typical distributed cache configurations configurable via @CacheConfig or jboss.xml; don't force users to go to a separate Infinispan configuration file.
The typical configurations are:
1) synchronous or async (perhaps a better term? async == fire and forget)
2) total replication or not?
3) if "not", number of backup copies.
Potentially 2 and 3 could be combined into a numbackups param:
-1 == total replication (i.e. unlimited)
0 == cache is in local mode
> 0 = DIST w/ numbackups + 1 copies.
--
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
14 years, 9 months