Last updated May 06, 2010 00:29, by Ken Cavanaugh
IIOP fail over and load balancing
- One-Pager is now available
- Basic model: bring over the features from GFv2
- Failover
- Required ORB code is already in place (unchanged from GFv2)
- Still need to enable ServerGroupManager in the orb-iiop bundles (in GlassFishORBManager)
- Need to revise ASORBUtilities to connect to GMS (class loading replaced with resource injection)
- Load balancing
- Mostly not handled in ORB
- Two exceptions:
- per-request load balancing (PRLB), which I added for Argela
- hardware loadbalancing support, which I added for NTT
- Two exceptions:
- Normal per InitialContext LB is entirely in naming
- Mostly not handled in ORB
- Testing
- ORB is well-covered for unit tests of failover components (RFM, ClientGroupManager, ServerGroupManager)
- GF-level testing has been handled entirely by SQE in the past
- Need developer tests for FOLB at GF level
- This needs a test framework for starting and stopping multiple GF instances, which may be on different hosts.
CSIv2 problems
- CSIv2 and IIOP FOLB have never worked together
- We should fix this
- Fix will probably align with moving parts of CSIv2 (mainly tagged component and service context related code) into the ORB
- This will simplify the current architecture, which has 2 code paths, one for CSIv2, and one for non-CSiv2
- Also provides a foundation for moving to Grizzly SSL, if we manage to get the ORB moved to Grizzly 2.0 someday.





