January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCLUSTER-135) Extract the common use clustering code from the JBoss AS codebase

by Brian Stansberry (JIRA)

Extract the common use clustering code from the JBoss AS codebase ----------------------------------------------------------------- Key: JBCLUSTER-135 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-135 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Critical Fix For: Q3Y6 Remoting, Messaging, JBoss Cache and JBoss AS all have clustering aspects to their functionality. There is potential for code reuse between these projects that can't be realized if the clustering code resides in the cluster module of the AS codebase. 1) Extract general purpose clustering code from the AS cluster module into a separate project and produce binaries that other projects can use without creating a dependence on the AS project. 2) Provide APIs that both support standalone functionality of non-AS projects and facilitate ease of integration into the AS. This task is meant to be an umbrella task, with specific detailed subtasks. This task is primarily focused on meeting the short requirements of JBMESSAGING-516, but we also need to give due consideration to potential use in other projects. -- 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

16 years, 11 months

2
4
0 / 0

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

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-97?page=all ] Brian Stansberry updated JBCLUSTER-97: -------------------------------------- Fix Version/s: Q1Y8 (was: Q4Y7) Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial, Compatibility/Configuration] (was: [Interactive Demo/Tutorial, Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration]) > Integrated Replication for EJB3 and HttpSession > ----------------------------------------------- > > Key: JBCLUSTER-97 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-97 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: Q1Y8 > > > 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. - 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCLUSTER-87) Fix netboot

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-87?page=all ] Brian Stansberry resolved JBCLUSTER-87. --------------------------------------- Fix Version/s: (was: Q3Y7) Resolution: Duplicate Issue The ProfileService replaces netboot. JBCLUSTER-117 better covers this general topic. > Fix netboot > ----------- > > Key: JBCLUSTER-87 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-87 > Project: JBoss Clustering > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Brian Stansberry > > self explanatory -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-128) Beautifying the UI for the FIELD-level http session replication example

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-128?page=all ] Brian Stansberry updated JBCLUSTER-128: --------------------------------------- Fix Version/s: Backlog (was: Q3Y7) Assignee: (was: Brian Stansberry) > Beautifying the UI for the FIELD-level http session replication example > ----------------------------------------------------------------------- > > Key: JBCLUSTER-128 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-128 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Priority: Minor > Fix For: Backlog > > > Currently in the http session field-level replication using JBossCache, we have a simple jsp to illustrate the fine-grained replication. However, it is not intuitive in that user can't see the real time field level change. What would be interesting is if we can somehow use a simple AJAX framework such that the change are repainted instantanesously. > Can we find a volunteer to do this? It would be a fun project and I can think can server as a very good tutorial article as well. > http://wiki.jboss.org/wiki/Wiki.jsp?page=Http_FIELD_level_replication (see the example at the end). -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-14) http session failover using single shared DB with cache loader

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-14?page=all ] Brian Stansberry updated JBCLUSTER-14: -------------------------------------- Fix Version/s: Backlog (was: Q3Y7) > http session failover using single shared DB with cache loader > -------------------------------------------------------------- > > Key: JBCLUSTER-14 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-14 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Tier > Reporter: Ben Wang > Assigned To: Brian Stansberry > Priority: Minor > Fix For: Backlog > > 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-129) Develop tests of the failover behavior of HTTP session replication under high memory and cpu load

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-129?page=all ] Brian Stansberry updated JBCLUSTER-129: --------------------------------------- Fix Version/s: Q1Y8 (was: Q3Y7) Assignee: Dominik Pospisil (was: Brian Stansberry) Dominik, this is an old JIRA that pretty much covers what you've been doing these last several months. So, I'm just assigning it to you. > Develop tests of the failover behavior of HTTP session replication under high memory and cpu load > ------------------------------------------------------------------------------------------------- > > Key: JBCLUSTER-129 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-129 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Dominik Pospisil > Fix For: Q1Y8 > > > Ensure reassignment of buddy replication buddies does not lead to cascading failures. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-130) Develop tests of the failover behavior of SFSB replication under high memory and cpu load

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-130?page=all ] Brian Stansberry updated JBCLUSTER-130: --------------------------------------- Fix Version/s: Q2Y8 (was: Q3Y7) Assignee: Dominik Pospisil (was: Brian Stansberry) Dominik, again this is an old JIRA that describes what you've been doing. > Develop tests of the failover behavior of SFSB replication under high memory and cpu load > ----------------------------------------------------------------------------------------- > > Key: JBCLUSTER-130 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-130 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Dominik Pospisil > Fix For: Q2Y8 > > > Ensure reassignment of buddy replication buddies does not lead to cascading failures. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-101) Make session clustering's "useJK" handling a pluggable policy so we can integrate with other load balancers

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-101?page=all ] Brian Stansberry updated JBCLUSTER-101: --------------------------------------- Fix Version/s: Q3Y8 (was: Q3Y7) > Make session clustering's "useJK" handling a pluggable policy so we can integrate with other load balancers > ----------------------------------------------------------------------------------------------------------- > > Key: JBCLUSTER-101 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-101 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Tier > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: Q3Y8 > > > Session replication uses the JvmRouteValve to detect session failover and modify the session id so mod_jk knows to thereafter pin the the session to the new node. > JBossCacheManager also has logic that understands how to strip out the jvmRoute from the session id. > Need to make this logic a pluggable policy, so we can deal with other load balancers that may have a different mechanism for tracking to which node a session is pinned. -- 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

16 years, 11 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-88?page=all ] Brian Stansberry updated JBCLUSTER-88: -------------------------------------- Fix Version/s: Backlog (was: Q3Y7) > Cluster configuration wizard > ---------------------------- > > Key: JBCLUSTER-88 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-88 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Brian Stansberry > 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. - 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

16 years, 11 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-84?page=all ] Brian Stansberry updated JBCLUSTER-84: -------------------------------------- Fix Version/s: Q1Y8 (was: Q3Y7) > Clustering monitor and management under JBoss ON > ------------------------------------------------ > > Key: JBCLUSTER-84 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-84 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Q1Y8 > > -- 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

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008