KbmMw 3.21 Full Source

Advanced loadbalancing demo --------------------------- Require kbmMW v2.5x ProPlus or Enterprise to compile. This demo contains two projects: 1) The AutoRegisteringLoadBalancer which is a loadbalancer that doesnt have a fixed knowledge about application servers. Instead the (clustered) application servers announce themself to the loadbalancer. The most important properties and settings are made in code, to make it easier to spot them. 2) The ClusteredServer which is a standard application server with a registered inventory and query service. In addition, it has a loadbalancer service which makes it possible for the learning autoregisteringloadbalancer to contact the application server to get to know about its status and health. To run: Default the loadbalancer is configured to listen on port 3010, and the clustered application server to listen on port 3000. However, as most demo client applications will connect to port 3000, and their first connection for this demo, should be the loadbalancer instead of an application server, you should specify to start the loadbalancer at port 3000 before clicking the listen button. You can start any number of clustered application servers up, just make sure, if they are started as the same machine as any other server incl. the loadbalancer, to give them a unique port number, and to point them to the right IP/port for the loadbalancer. The loadbalancer is configured to use the Round Robin allocation algorithm, which means that each time a client connects to the loadbalancer, the client will be redirected to the next available application server in line. I.e. 1st client connection will get to cluster server 1, 2nd client connection will get to cluster server 2, etc. For the client to autoreconnect when the application server its using is disappearing/crashing/shutting down, the client should be configured with a MaxRetries of no less than 2, and MaxAltRetries of no less than 1. In the OnReconnect event of the client transport, there should be put code to setup the client transport to point at a loadbalancer when the Alt argument is true (ie. an alternative reconnect try is about to happen). The default demo client applications dont have this coded in. For more information, please read the 'Failover and loadbalancing' whitepaper. best regards Kim Madsen kbm@components4developers.com