July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7272) Handle MergeViews in AbstractClusterLockSupport variants

by Brian Stansberry (JIRA)

Handle MergeViews in AbstractClusterLockSupport variants -------------------------------------------------------- Key: JBAS-7272 URL: https://jira.jboss.org/jira/browse/JBAS-7272 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 org.jboss.ha.framework.server.lock.AbstractClusterLockSupport and/or its subclasses need to deal with cluster merges, i.e. AS instances in groups {A, B} and {C, D} discover each other and form a single group {A, B, C, D}. Following a merge, it's possible a node in each of the merged subgroups thinks it has the cluster wide lock. A simple approach that *may* work in all cases is to handle a merge by having each node abandon the cluster-wide lock, forcing the next attempt by a local caller to re-acquire the lock. Need to think through though whether that is the correct semantic in all cases. AbstractClusterLockSupport needs to implement HAExtendedMembershipListener instead of just HAMembershipListener; this will allow it to know whether a view change was due to a merge. -- 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

1
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-188) Possible further extraction of clustering code from AS codebase

by Brian Stansberry (JIRA)

Possible further extraction of clustering code from AS codebase --------------------------------------------------------------- Key: JBCLUSTER-188 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-188 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y8 Container task for evaluating further extractions. -- 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

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-184) Explore use of ClusteredCacheLoader to avoid state transfer

by Brian Stansberry (JIRA)

Explore use of ClusteredCacheLoader to avoid state transfer ----------------------------------------------------------- Key: JBCLUSTER-184 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-184 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry With CCL a cache miss results in a get call around the cluster. Can eliminate the need for in-memory state transfer. Won't work with buddy replication, but could be very interesting with total replication. Need to think through issues with things like passivation. -- 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

14 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-140) Examine need for a distributed service registry outside the AS

by Brian Stansberry (JIRA)

Examine need for a distributed service registry outside the AS -------------------------------------------------------------- Key: JBCLUSTER-140 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-140 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Is something like DRM needed outside the AS? If it is, do we want to use the JBoss Cache based version (creates JBC dependency.) DRM is used in two ways: 1) To maintain a distributed registry of remote invocation targets. 2) To maintain a distributed registry of services, which is done by having the service register a meaningless token under its key rather than a target. This is used by HASingleton. Need to examine whether this kind of thing is needed by Messaging, or whether simple listening for view changes is sufficient. Listening for view changes could be sufficient if each group member knew how to create a Remoting InvokerLocator for the other members based on the JGroups Address. But, this presupposes use of consistent ports across the cluster, and that the IP address used by JGroups is the one that Messaging traffic should use. -- 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

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-144) Consider other clustering code that can be removed from the AS

by Brian Stansberry (JIRA)

Consider other clustering code that can be removed from the AS -------------------------------------------------------------- Key: JBCLUSTER-144 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-144 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q4Y6 Things like the http session replication code that we've considered integrating into Tomcat. -- 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

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Resolved: (JBCLUSTER-84) Clustering monitor and management under JBoss ON

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBCLUSTER-84?page=com.atlassian.jira.plug... ] Brian Stansberry resolved JBCLUSTER-84. --------------------------------------- Resolution: Out of Date > Clustering monitor and management under JBoss ON > ------------------------------------------------ > > Key: JBCLUSTER-84 > URL: https://issues.jboss.org/browse/JBCLUSTER-84 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assignee: Brian Stansberry > Fix For: Legacy > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBCLUSTER-97) Integrated Replication for EJB3 and HttpSession

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBCLUSTER-97?page=com.atlassian.jira.plug... ] Brian Stansberry reassigned JBCLUSTER-97: ----------------------------------------- Assignee: (was: Brian Stansberry) > Integrated Replication for EJB3 and HttpSession > ----------------------------------------------- > > Key: JBCLUSTER-97 > URL: https://issues.jboss.org/browse/JBCLUSTER-97 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Fix For: Legacy > > > We need to have the ability to replicate any EJB3 and http session state changes associated with a request at the same time. Otherwise, we just double the replication-related latency of the request. This is critical in the case of SEAM. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBCLUSTER-88) Cluster configuration wizard

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBCLUSTER-88?page=com.atlassian.jira.plug... ] Brian Stansberry reassigned JBCLUSTER-88: ----------------------------------------- Assignee: (was: Brian Stansberry) > Cluster configuration wizard > ---------------------------- > > Key: JBCLUSTER-88 > URL: https://issues.jboss.org/browse/JBCLUSTER-88 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Fix For: Backlog > > > Maybe in collaboration with JBoss Network (or maybe they are working on it). > - Tool to configure clustering, generates e.g. cluster-service.xml file > - First pick what needs to be clustered, e.g. base clustering (HA-JNDI etc), HTTP session replication, clustered EJB3 etc > - Then, for each cluster, configure: > - what transport (default) > - what bind address (tool should probe for NIC and display them in a list) > - for TCP: list of nodes > - If TCP: no FRAG, no UNICAST > - If UDP: what mcast address, TTL, port > - Wizard should run sanity tests after config, e.g. are clusters cleanly separated ? > - Wizard should provide defaults, so pressing Enter on every decision leads to the default clustering config > - Wizard should also be able to parse existing config, and reconfig it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-141) Create a generic HA Singleton API

by Brian Stansberry (JIRA)

Create a generic HA Singleton API --------------------------------- Key: JBCLUSTER-141 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-141 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Also want to extract the HASingletonElectionPolicy code from the AS codebase. -- 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

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Assigned: (JBCLUSTER-78) Handling of merge

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBCLUSTER-78?page=com.atlassian.jira.plug... ] Brian Stansberry reassigned JBCLUSTER-78: ----------------------------------------- Assignee: (was: Brian Stansberry) > Handling of merge > ----------------- > > Key: JBCLUSTER-78 > URL: https://issues.jboss.org/browse/JBCLUSTER-78 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Fix For: Legacy > > > All building blocks which involve state do *not* implement handling of merging. E.g. DRM.mergeMembers() should invoke a callback so that each subscribed listener can handle the merge. > This needs to be done for the existing building blocks for backward compatibility, the new mechanism used is JBossCache (see link) which will handle state merging -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011