• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Running WO
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Running WO


  • Subject: Re: Running WO
  • From: "Pierce T. Wetter III" <email@hidden>
  • Date: Tue, 6 Jun 2006 07:54:34 -0700


On Jun 6, 2006, at 7:25 AM, Paul Lynch wrote:


On 6 Jun 2006, at 12:57, Frank Gibau wrote:

WO-Deployment.
We run WO an two G5 (Dual) with MacOS-X-Server-Software. On each computer (WO1, WO2) we have 8 instances of our applictation running. One computer (WO1) ist running WOMonitor to manage the load balancing.
We want to install a third computer (G5). Must we install MacOS X- Server on this computer or could we use an normal MacOS X System ?. Has MacOS X-Server-Sortware an advantage ?.
What is the best laod balancing method for 3 or more WO Server?

You can use plain MacOS X. Server has only minor advantages, which mainly come down to various preinstalled utilities, and the Server Admin app. If you have any familiarity with Unix systems at all, you might as well avoid the extra cost of MacOS X Server.


Depending on what you mean by load balancing (saying that JavaMonitor is managing load balancing implies that you may have a slightly different meaning from me), just create a reasonable number of instances on the new server, and use round-robin. In other words, the same as for two servers, and not significantly different from one server.


 When using round-robin, be sure and do:

 instance 1:  machine 1   port 1000
 instance 2:  machine 2   port 1000
 instance 3:  machine 1   port 1001
 instance 4:  machine 2   port 1001

That is, interleave the machines with the instances. Otherwise, if you're running several instances on one machine:

 instance 1:  machine 1   port 1000
 instance 2:  machine 1   port 1001
 instance 3:  machine 1   port 1002

Then all the requests will first go to machine 1, then machine 2, rather then distributing among machines.

Similarly, if you have multiple webservers in front of the instances for redundancy, random may work better, since the webservers have no way to coordinate unless you create a custom XML file for each webserver so that their round robin doesn't work in parallel.

Personally, in production, I've found that its better to use an XML file on the webserver and shell scripts on the application machines then to fuss with JavaMonitor.

Pierce



WOTip: Don't use load balancing in the adaptor. Use roundrobin.
More Tips: http://www.twinforces.com




_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Running WO (From: Frank Gibau <email@hidden>)
 >Re: Running WO (From: Paul Lynch <email@hidden>)

  • Prev by Date: Re: Running WO
  • Next by Date: Re: Running WO
  • Previous by thread: Re: Running WO
  • Next by thread: Re: Running WO
  • Index(es):
    • Date
    • Thread