[JBoss JIRA] Updated: (JBCACHE-64) Region-based cache
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-64?page=all ]
Manik Surtani updated JBCACHE-64:
---------------------------------
Fix Version/s: 3.x
(was: 2.3.0.GA)
Description:
refactor Region to make it generic to configuration such as persistency,
eviction policy, replication mode, transaction isolation level, etc. Example,
we can have one "transient" region and one "replicated" region.
See:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheRegions
was:
refactor Region to make it generic to configuration such as persistency,
eviction policy, replication mode, transaction isolation level, etc. Example,
we can have one "transient" region and one "replicated" region.
Complexity: High
> Region-based cache
> ------------------
>
> Key: JBCACHE-64
> URL: http://jira.jboss.com/jira/browse/JBCACHE-64
> Project: JBoss Cache
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assigned To: Manik Surtani
> Fix For: 3.x
>
>
> refactor Region to make it generic to configuration such as persistency,
> eviction policy, replication mode, transaction isolation level, etc. Example,
> we can have one "transient" region and one "replicated" region.
> See:
> http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheRegions
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years
[JBoss JIRA] Created: (JBAS-4574) AS ejb ha restart would fail
by Ben Wang (JIRA)
AS ejb ha restart would fail
----------------------------
Key: JBAS-4574
URL: http://jira.jboss.com/jira/browse/JBAS-4574
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.0.5.GA
Reporter: Ben Wang
Assigned To: Ben Wang
This is an issue discovered during a pre-sales opportunity. Basically, it can be reproduced like this:
1. Use a web tier (calling remote slsb ejb from jsp, e.g.) with 2 ejb tiers (for clustering, say, ejb1, ejb2)
2. access it first to ejb1
3. shutdown ejb1, and access it again will failover to ejb2
4. shutdown ejb2 and bring up ejb1, should produce error traces (I don't have now). Will attach it here later.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years