March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCLUSTER-60) Packaging standalone tc5 http session replication using JBossCache

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-60?page=all ] Brian Stansberry updated JBCLUSTER-60: -------------------------------------- Fix Version/s: (was: Q1Y7) Dropping from schedule, as this is not a current priority. > Packaging standalone tc5 http session replication using JBossCache > ------------------------------------------------------------------ > > Key: JBCLUSTER-60 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-60 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Original Estimate: 3 days > Remaining Estimate: 3 days > > Brian will own this. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-13) Standalone Tomcat http session replication using JBossCache

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-13?page=all ] Brian Stansberry updated JBCLUSTER-13: -------------------------------------- Fix Version/s: (was: Q1Y7) Dropping from the schedule, as this is not a current priority. > Standalone Tomcat http session replication using JBossCache > ----------------------------------------------------------- > > Key: JBCLUSTER-13 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-13 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Original Estimate: 5 weeks > Remaining Estimate: 5 weeks > > Porting the current http session replication implementation to Tomcat standalone. -- 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, 3 months

1
0
0 / 0

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

by Sam Wilson (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-87?page=comments#action_12356762 ] Sam Wilson commented on JBCLUSTER-87: ------------------------------------- That's great news. Unfortunately, in the year or so since I posted this, I've already moved away from JBoss as a viable target platform. > 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 > Fix For: Q3Y7 > > > 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

19 years, 3 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: -------------------------------------- Summary: Handling of merge (was: Handling of merge (currently only done in DistributedReplicantManager)) Fix Version/s: Q3Y7 Updating to serve as a container task for state-merge related issues. > 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: Q3Y7 > > > 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-78) Handling of merge (currently only done in DistributedReplicantManager)

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-78?page=all ] Brian Stansberry updated JBCLUSTER-78: -------------------------------------- Comment: was deleted > Handling of merge (currently only done in DistributedReplicantManager) > ---------------------------------------------------------------------- > > 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: Q3Y7 > > > 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

19 years, 3 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-26?page=all ] Brian Stansberry updated JBCLUSTER-26: -------------------------------------- Fix Version/s: Q3Y7 (was: Q4Y6) > farming 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: Q3Y7 > > 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

19 years, 3 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-87?page=all ] Brian Stansberry updated JBCLUSTER-87: -------------------------------------- Fix Version/s: Q3Y7 (was: Q4Y6) I'll look at netboot as part of work on AS 5 deployment issues and the ProfileService. > 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 > Fix For: Q3Y7 > > > 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

19 years, 3 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: Q3Y7 (was: Q4Y6) > 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: Q3Y7 > > > 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-10) Unified client side failover/load-balancing on top of Remoting

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-10?page=all ] Brian Stansberry updated JBCLUSTER-10: -------------------------------------- Fix Version/s: Q2Y7 (was: Q4Y6) > Unified client side failover/load-balancing on top of Remoting > -------------------------------------------------------------- > > Key: JBCLUSTER-10 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-10 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Q2Y7 > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Bill has a version that does this using the Remoting transport framework implemented in ejb3. Need further documentation and testing. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-72) Certify JBoss Clustering Content on JBoss Labs

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-72?page=all ] Brian Stansberry updated JBCLUSTER-72: -------------------------------------- Fix Version/s: Q3Y7 (was: Q4Y6) > Certify JBoss Clustering Content on JBoss Labs > ---------------------------------------------- > > Key: JBCLUSTER-72 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-72 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Damon Sicore > Assigned To: Brian Stansberry > Fix For: Q3Y7 > > > See incorporated task for instructions. -- 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, 3 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 March 2007