[ http://jira.jboss.com/jira/browse/JBCLUSTER-101?page=all ]
Brian Stansberry updated JBCLUSTER-101:
---------------------------------------
Fix Version/s: Q3Y7
(was: Q4Y6)
> 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)
> Reporter: Brian Stansberry
> Assigned To: Brian Stansberry
> Fix For: Q3Y7
>
>
> 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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-128?page=all ]
Brian Stansberry updated JBCLUSTER-128:
---------------------------------------
Fix Version/s: Q3Y7
(was: Q4Y6)
> 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
> Assigned To: Brian Stansberry
> Priority: Minor
> Fix For: Q3Y7
>
>
> 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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-84?page=all ]
Brian Stansberry updated JBCLUSTER-84:
--------------------------------------
Fix Version/s: Q3Y7
(was: Q4Y6)
> 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: Q3Y7
>
>
--
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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-130?page=all ]
Brian Stansberry updated JBCLUSTER-130:
---------------------------------------
Fix Version/s: Q3Y7
(was: Q4Y6)
> 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: Brian Stansberry
> Fix For: Q3Y7
>
>
> 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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-20?page=all ]
Brian Stansberry updated JBCLUSTER-20:
--------------------------------------
Fix Version/s: Q2Y7
(was: Q4Y6)
Pushing to Q2. Jason, you can re-schedule as you feel appropriate.
> Create a specialized version of TreeCacheAopViewer
> --------------------------------------------------
>
> Key: JBCLUSTER-20
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-20
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Jason T. Greene
> Priority: Minor
> Fix For: Q2Y7
>
> Original Estimate: 4 weeks
> Remaining Estimate: 4 weeks
>
> that can either view the http session contents or even SFSB contents. This can be useful for debugging and development purpose.
--
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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-129?page=all ]
Brian Stansberry updated JBCLUSTER-129:
---------------------------------------
Fix Version/s: Q3Y7
(was: Q4Y6)
> 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: Brian Stansberry
> Fix For: Q3Y7
>
>
> 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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-30?page=all ]
Brian Stansberry updated JBCLUSTER-30:
--------------------------------------
Fix Version/s: Q2Y7
(was: Q4Y6)
> EJB3.0 and 2.1 clustering integration
> -------------------------------------
>
> Key: JBCLUSTER-30
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-30
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Ben Wang
> Fix For: Q2Y7
>
> Original Estimate: 6 weeks
> Remaining Estimate: 6 weeks
>
> Future ejb3.0 will run along side ejb2.1. In terms of clustering offering, ejb2.1 SFSB and entity bean will use the original implementation while 3.0 will use JBossCache and Hibernate. What's the clustering implication and integration needs? Or just pure documentation?
--
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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-119?page=all ]
Brian Stansberry updated JBCLUSTER-119:
---------------------------------------
Fix Version/s: Q2Y7
(was: Q4Y6)
> Effect of different JGroups transports
> --------------------------------------
>
> Key: JBCLUSTER-119
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-119
> Project: JBoss Clustering
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Brian Stansberry
> Assigned To: Brian Stansberry
> Fix For: Q2Y7
>
> Attachments: ResultsExtract.pdf, tc5-cluster-service.xml.nio, tc5-cluster-service.xml.tcp, tc5-cluster-service.xml.udp
>
>
> Need to see in which cluster topologies UDP, TCP and TCP_NIO perform best. Particularly, how big of a cluster before UDP pays off. Need to factor buddy replication into 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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-110?page=all ]
Brian Stansberry updated JBCLUSTER-110:
---------------------------------------
Fix Version/s: Q2Y7
(was: Q4Y6)
> HttpSession sharing between WAR modules
> ---------------------------------------
>
> Key: JBCLUSTER-110
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-110
> Project: JBoss Clustering
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Brian Stansberry
> Assigned To: Brian Stansberry
> Fix For: Q2Y7
>
>
> Companion task for JBAS-2861 so we can track it on the big-picture clustering 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
[ http://jira.jboss.com/jira/browse/JBCLUSTER-6?page=all ]
Brian Stansberry updated JBCLUSTER-6:
-------------------------------------
Fix Version/s: Q2Y7
(was: Q4Y6)
> Refactor DistributedReplicationManager (DRM) if necessary
> ---------------------------------------------------------
>
> Key: JBCLUSTER-6
> URL: http://jira.jboss.com/jira/browse/JBCLUSTER-6
> Project: JBoss Clustering
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Assigned To: Jerry Gauthier
> Fix For: Q2Y7
>
>
> DistributedReplicationManager currently doesn't fit into the JBossCache as the underlying framework. Will need to look into this how to integrate 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