[jboss-cvs] contrib/varia/src/resources/loadbalancer/docs loadbalancer.txt loadbalancer.doc

[Thomas P. <tp...@us...>]

  User: tpeuss  
  Date: 04/03/07 07:53:49

  Modified:    varia/src/resources/loadbalancer/docs loadbalancer.txt
  Removed:     varia/src/resources/loadbalancer/docs loadbalancer.doc
  Log:
  Docs are now in the JBoss Wiki.
  
  Revision  Changes    Path
  1.4       +1 -19     contrib/varia/src/resources/loadbalancer/docs/loadbalancer.txt
  
  Index: loadbalancer.txt
  ===================================================================
  RCS file: /cvsroot/jboss/contrib/varia/src/resources/loadbalancer/docs/loadbalancer.txt,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- loadbalancer.txt	29 Feb 2004 19:24:02 -0000	1.3
  +++ loadbalancer.txt	7 Mar 2004 15:53:49 -0000	1.4
  @@ -1,19 +1 @@
  -Loadbalancer-Service
  -The Loadbalancer-Service provides reverse-proxy support with silent failover.
  -The files sit in the directory {jboss-home}/docs/examples/varia/loadbalancer/.
  -Configuration of the Loadbalancer
  -Copy the directory loadbalancer.sar to your deploy directory. Edit loadbalancer.sar/META-INF/jboss-service.xml to match your configuration.
  -Connection-timeout
  -The connection-timeout controls after which time interval a host should be considered dead. This value is given in milliseconds.
  -Sticky-sessions and sticky session cookie name
  -This value (true or false is allowed) controls if a request should always go to the host the client is first scheduled on. This is needed if you use HTTP-sessions in your web-application. If you set this value to false every request is rescheduled with the algorithm given in the scheduler class. The session cookie name sets the name of the cookie the sticky session information is stored in.
  -Hosts list
  -The hosts given in this list are used as request targets.  The URLs can be of any type a normal web-browser will accept (http://www.xy.zz/, https://www.xy.zz/, http://www.xy.zz:8080/). The loadbalance-factor is not used at this time but will be used by later schedulers.
  -
  -Monitor Services
  -There are two monitor services available that check the availability of the target nodes in given intervals. They can be enabled by uncommenting them in jboss-service.xml. This services work in both ways - they mark up nodes down and the other way round if certain conditions are met.
  -SimpleMonitorService
  -This monitor checks that a given path on a target node is reachable (gives a HTTP response like OK or MOVED).
  -ECVMonitorService 
  -The ECVMonitorService (ECV=Extended Content Verification) does the same like the SimpleMonitorService but does additional checks on the webserver response. It tries to match a given regular expression against the server response. This can something like ".*HELLO.*WORLD.*" or just a simple word like "JBoss".
  -
  +See http://jboss.org/wiki/Wiki.jsp?page=HTTPLoadbalancer for documentation.