January 2008 - jboss-jira - Jboss List Archives

[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

18 years, 6 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

18 years, 6 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-69) Create an analysis comparing HttpSession replication in JBoss to BEA's implementation

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-69?page=all ] Brian Stansberry updated JBCLUSTER-69: -------------------------------------- Fix Version/s: Q3Y8 (was: Q3Y7) > Create an analysis comparing HttpSession replication in JBoss to BEA's implementation > ------------------------------------------------------------------------------------- > > Key: JBCLUSTER-69 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-69 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: Q3Y8 > > > We need to compare the features/capabilities of our session replication approach to BEA's. The results of the analysis should be a driver for the session replication roadmap. -- 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

18 years, 6 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-78?page=all ] Brian Stansberry updated JBCLUSTER-78: -------------------------------------- Fix Version/s: Q3Y8 (was: Q3Y7) Moving to Q3 calendar 2008 (which is optimistic) > Handling of merge > ----------------- > > Key: JBCLUSTER-78 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-78 > Project: JBoss Clustering > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assigned To: Brian Stansberry > Fix For: Q3Y8 > > > 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. - 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-54) JGroups and JBoss Cache config best practice

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-54?page=all ] Brian Stansberry updated JBCLUSTER-54: -------------------------------------- Fix Version/s: Q2Y8 (was: Q4Y7) > JGroups and JBoss Cache config best practice > -------------------------------------------- > > Key: JBCLUSTER-54 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-54 > Project: JBoss Clustering > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: Q2Y5 > Reporter: Michael Yuan > Assigned To: Brian Stansberry > Fix For: Q2Y8 > > > We need a set of "Best Practices" on how to set various parameters on the JGroups and JBoss Cache MBean attributes. I think the "Best Practice" guide can take the format of a FAQ: > Q: Describe a common clustering error message or low performance scenario > A: Discuss possible reasons and MBean configuration parameters to adjust to solve this problem. -- 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-51) Provide documentation to the Clustering Guide

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-51?page=all ] Brian Stansberry updated JBCLUSTER-51: -------------------------------------- Fix Version/s: Q2Y8 (was: Q3Y7) > Provide documentation to the Clustering Guide > --------------------------------------------- > > Key: JBCLUSTER-51 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-51 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: Q2Y5 > Reporter: Michael Yuan > Assigned To: Brian Stansberry > Fix For: Q2Y8 > > > This task provides a central place to manager all issues related to the "Clustering Guide" document. Specific requests are made in the sub-tasks. -- 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-12) Clustering statistics and monitoring

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-12?page=all ] Brian Stansberry updated JBCLUSTER-12: -------------------------------------- Fix Version/s: Q2Y8 (was: Q3Y7) > Clustering statistics and monitoring > ------------------------------------ > > Key: JBCLUSTER-12 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-12 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Q2Y8 > > > Need to implement cluster-related management attributes for tuning and monitoring. Will also need JBossCache and JGroups ones. -- 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-26) Clustered deployments should be atomic

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-26?page=all ] Brian Stansberry updated JBCLUSTER-26: -------------------------------------- Summary: Clustered deployments should be atomic (was: farming should be atomic) Fix Version/s: Q2Y8 (was: Q3Y7) > Clustered deployments should be atomic > -------------------------------------- > > Key: JBCLUSTER-26 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-26 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Priority: Critical > Fix For: Q2Y8 > > Original Estimate: 8 weeks > Remaining Estimate: 8 weeks > > Our current farm deployment is not automic, meaning that one cluster node failed, it won't rollback the rest within the cluster. > One soultion is make the deployer XA resource so they can participate in sort of 2 phase commit. > This can potentially be applied to MBean clustering as well. > In addition, farming service has couple bugs outstanding. It needs an overhaul as well. -- 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-115) Major Clustering Features in JBoss 5.0

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-115?page=all ] Brian Stansberry updated JBCLUSTER-115: --------------------------------------- Fix Version/s: Q2Y8 (was: Q3Y7) > Major Clustering Features in JBoss 5.0 > -------------------------------------- > > Key: JBCLUSTER-115 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-115 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Blocker > Fix For: Q2Y8 > > > Overall tracking issue for *major* clustering features/fixes to be included in JBoss AS 5.0.0. > There will of course be numerous minor issues; please track those with a filter on the issues in the JBAS project. -- 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

18 years, 6 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 January 2008