Hi!

  Talk about digging up old threads! :P

  It's sufficient. I don't really remember all the details now, but having that 
on the apps is sufficient. You may have to set -WOHost on the wotaskd to a host 
in the same network as the apps, but try it cleanly first.

  Regards,

Miguel Arroz

On 2010/11/19, at 21:11, Kieran Kelleher wrote:

> I had forgotten about that thread and it did not show up in my search!
> 
> included it in local ERExtensions and deploying test bundle now........ do I 
> need to build wotaskd with this too ... or is the app.woa sifficient?
> 
> 
> 
> On Nov 19, 2010, at 2:20 PM, Chuck Hill wrote:
> 
>> Hey Kieran,
>> 
>> Try to launch wotaskd and the apps with the flags -WOHost 127.0.0.1. We have 
>> discovered recently that, in a multi-homed machine, Java will not recognize 
>> some of the machine IPs as being "localhost". This causes the apps to refuse 
>> management requests, which means they cannot be terminated, put in "refuse 
>> new sessions" mode, etc.
>> 
>> We didn't want to run the apps in the 127.0.0.1 IP for network configuration 
>> reasons, so we, errr, wrote the following class. Make sure it loads before 
>> the WO frameworks. Check the javadoc for details, and change the property 
>> name please! ;)
>> 
>> I was going to submit this to Wonder but still didn't have time, anyway, 
>> Mike, Anjo, anyone, if you want to grab this and add it to Wonder, please do 
>> go ahead.
>> 
>> <WOHostUtilities.java>
>> 
>> Yours
>> 
>> Miguel Arroz
>> 
>> 
>> 
>> On 2010/02/01, at 18:44, Kieran Kelleher wrote:
>> 
>>> Before I go off deploying my own Wonder version of wotaskd with a bunch of 
>>> debugging stuff, perhaps someone has some obvious things to check for the 
>>> following problem:
>>> 
>>> I have apple wotaskd 5.4.3 and womonitor 5.4.3 on a Mac OS X machine. The 
>>> other machines in this server group are Mac OS X and there is just one 
>>> Linux Centos VM (The VM runs on OS X machine).
>>> 
>>> For the Linux Centos host, all WOMonitor functionality works fine with the 
>>> exception of shutdown the instance. Nothing happens when "Stop" is clicked. 
>>> So, to stop or restart, I have to go and kill it on the command line. Any 
>>> ideas for a "quick fix" for this (assuming this works fine for everyone 
>>> else using Centos Linux WebObjects nodes)
>>> 
>>> Regards, Kieran _______________________________________________
>>> 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/arroz%40guiamac.com
>>> 
>>> This email sent to [email protected]
>> 
>> 
>> _______________________________________________
>> 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/chill%40global-village.net
>> 
>> This email sent to [email protected] 
>> _______________________________________________
>> 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/kelleherk%40gmail.com
>> 
>> This email sent to [email protected]
> 


 _______________________________________________
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]

Reply via email to