On 2012-02-28, at 1:41 PM, Gaastra Dennis - WO Lists wrote:

> Hi Chuck,
> 
> Thanks that partially worked. To make the configs as host neutral as 
> possible, I did:
> 
> Edit File, nano 
> /Library/WebObjects/Deployment/wotaskd.woa/Contents/Resources/Properties, 
> added bottom two lines:
> 
> WOSMTPHost = localhost
> WOHost = localhost
> 
> Edit File, nano 
> /Library/WebObjects/Deployment/JavaMonitor.woa/Contents/Resources/Properties, 
> add bottom line:
> 
> WOHost = localhost
> 
> However, then in monitor, the instances did not work anymore at the FDN, so 
> had to add host "localhost" instead, and then everything worked. However, now 
> I cannot access monitor remotely anymore...

Yes, that is why you don't want to use localhost.  :-)


> So what would be the most host-neutral way, to get this to work. With 
> Leopard, we never had any problems or needed to complete any settings like 
> this.

It can't be host neutral.  It needs to be consistent, and it needs to be 
correct with a reverse DNS lookup.  And these problems were seen with Leopard 
and before, this is not at all new.  Network loading and initialization order 
and timing can have great effect which is why you want to explicitly set the 
names being used.


Chuck


> On 27/Feb/12 5:17 PM, Chuck Hill wrote:
>> That sounds like JavaMonitor and wotaskd and the instances don't have a 
>> common (or correct) WOHost name in their Properties files.
>> 
>> 
>> Chuck
>> 
>> 
>> On 2012-02-28, at 7:02 AM, Gaastra Dennis - WO Lists wrote:
>> 
>>> Dear List,
>>> 
>>> Just upgrading several boxes to Lion Server.
>>> We applied the standard WO543 Installer and Ken's Wonder wotaskd and 
>>> WOMonitor from:
>>> 
>>> http://www.ksroom.com/App/WebObjects/Kisa.woa/wa/woDeploy
>>> 
>>> BTW: Thanks for making this available
>>> 
>>> When clicking on:
>>> 
>>> http://localhost:1085/cgi-bin/WebObjects/wotaskd.woa/wa/woconfig
>>> 
>>> We see our configured instances nicely listed; however, in Monitor, we all 
>>> instances "Off" with 1 "Death" for each.
>>> Also, the URLs (from remotely) don't work and show: The requested 
>>> application was not found on this server.
>>> However, in the application instances' log, everything starts up  and stays 
>>> running nicely.
>>> Also,  the instances are running correctly according to ps -ax or sudo lsof 
>>> -i tcp:
>>> I don't understand how to debug this; already tried the spawof...ssh, and 
>>> there everything was OK. Also DNS is working correclty both ways.
>>> 
>>> Another weird this is that one of the boxes works correctly every 5 reboots 
>>> or so.
>>> 
>>> Any ideas? Thanks for any assistance.
>>> 
>>> 
>>> -- 
>>> With Kind Regards,
>>> 
>>> Dennis Gaastra,
>>> WEBAPPZ®  Systems, Inc.
>>> (+1) 604.921.1333
>>> 
>>> www.webappz.com&  www.scheduleDS.com&  www.1tracker.com
>>> 
>>> 
>>> 

-- 
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall 
knowledge of WebObjects or who are trying to solve specific problems.    
http://www.global-village.net/gvc/practical_webobjects








Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to