What I was talking about were multiple deployment instances on multiple machines - they just happen to be used for testing by our developers.
For example, we have a machine named Bart. Bart is running an app called HR, and the adapter is configured for a Host List with the following in the apache.conf file: WebObjectsConfig http://10.1.254.10:1085 10 Monitor is running on Bart as well. Lisa is a separate machine running an app called Finance. Lisa's adapter is also configured for a Host List with the following in 'her' apache.conf file: WebObjectsConfig http://10.1.254.11:1085 10 Monitor is running on Lisa as well. The problem is that Bart, from time to time, learns about the Finance app running on Lisa, and decides to add it to the SiteConfig.xml and take ownership of it. The opposite has also happened, where Lisa assumes ownership of HR. Neither is desirable. As I understand it now, the doc on "Deploying Multiple Sites" applies to multiple sites on the same subnet as well as multiple sites on the same hardware... Thanks, John -----Original Message----- From: Mark Ritchie [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 7:49 PM To: Atkinson John-HKV437 Cc: [email protected] Subject: Re: Multiple JavaMonitor instances on the same subnet On 12-Mar-07, at 7:07 PM, Atkinson John-HKV437 wrote: > ... WO development environments ... Hrm, do you mean development instances or deployment instances? Development instances do some pretty special things compared with deployment instances started by wotaskd. As Cliff pointed out, JavaMonitor is kinda particular about not 'sharing' with another instance of JavaMonitor. That being said, if you're talking about deployment, there are docs on "Deploying Multiple Sites" on a single machine: http://developer.apple.com/documentation/WebObjects/Deployment/ Deploying_Applications/Deployment/chapter_6_section_8.html > ... basically screwing things up ... Could you be more specific about what seems to be the trouble. There are many things which could appear 'screwed up'. :-) Some basics to check: - look at WOAdaptorInfo on each web server (yes, each and every one - a recent client was round robin'ing to 6 web servers and every one of them had a different configuration - fun... NOT!) - for each wotaskd listed on the WOAdaptorInfo pages, check what's returned by the configuration URI something like: http://appserver_name:_taskd_port/cgi-bin/WebObjects/wotaskd.woa/wa/ woconfig (This is how the WOAdaptor gets the list of which apps are running and their details.) - Check that each instance of wotaskd on a single machine has different settings for: WOPort WODeploymentConfigurationDirectory - Check that each instance of JavaMonitor has proper settings for: WOLifebeatDestinationPort WODeploymentConfigurationDirectory (mutually exclusive for each instance of JavaMonitor.) - Make sure that each instance of JavaMonitor is controlling separate wotaskd instances. (Make a change and check the appropriate site configuration file.) - change .../wotaskd.woa/Contents/Resources/SpawnOfWotaskd.{sh,exe} (platform specific) to log any startup troubles - turn on logging for application instances and check the logs for errors Sorry, now I'm just getting silly... Really should have completed that "field survival guide to deployment" handbook that I was working on years ago. Good luck! Mark __ Mark Ritchie Cocoa and WebObjects Developer Diamond Lake Consulting Inc. Toronto, Ontario, Canada _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [email protected]
