When you run a single instance, does it also require the port
number in the URL? Are you launching wo(e)taskd with -
WOHost=localhost as well?
Chuck
Thanks for all your help Chuck,
Yes, it does require the port number in the URL.
Then it is not going through wotaskd normally.
*gulp* What did we do wrong...
Adding WOHost localhost in System/Library/StartupItems/WebObjects/
WebObjects didn't work. I then added it in the other place (now both
places have the WOHost argument), but to no avail. I noticed the
first method is WOHost localhost and the other one (in Properties) is
WOHost=localhost. Is that right?
Here's the log from WebObjects.log (PS - I tried doing that a while
ago but couldn't get the dang log file to appear even after several
attempts to connect to the app... but this time, it worked!)
Info: <WebObjects Apache Module> new request: /cgi-bin/WebObjects/
Meneda.woa
Debug: App Name: Meneda.woa (6)
Info: Specific instance Meneda: not found. Reloading config.
Debug: Checking config file /Library/WebObjects/Configuration/
Debug: Checking config /Library/WebObjects/Configuration/
Debug: Checking config /Library/WebObjects/Configuration/ mod time
Info: Reading configuration from /Library/WebObjects/Configuration/
Error: Error reading /Library/WebObjects/Configuration/: Operation
not permitted
Debug: Checking config /tmp/WebObjects.xml
Debug: stat call failed on /tmp/WebObjects.xml (errno=2)
Error: Request handling error: The requested application was not
found on this server.
Because of the Operation not permitted, I tried to chmod 777 the
files and folders in /Library/WebObjects/Configuration/ where the
Site and WOConfig xml files are, but it still gives me the same
thing. The log only records all this when I try to connect to the app
in question (I guess that's to be expected).
Hopefully it will give you an idea of what the problem could be. I
can't say how thankful I am for your time and help!
Regarding the launch of wotaskd, JavaMonitor and Wotaskd were set
to launch on system startup by removing #s in a configuration file
(we're running MacOSXServer10.3.9), we do everything in
JavaMonitor. We also added the WOConfig.xml file with instances
specs. I'm not sure if I'm actually launching wotaskd with -
WOHost=localhost, but I did include it in the only place I know in
JavaMonitor, the Additional Arguments in the Application settings
where we also set the password.
Perhaps this is our problem... How does one set -WOHost=localhost
on wotaskd launch (is there a way to configure it on system
startup)? Does it require the command-line in Terminal?
You can set this in a few different ways. One is to edit the file
/System/Library/StartupItems/WebObjects/WebObjects
And add it to the wotaskd line like this
"$WOSERVICE" -appPath "$WOTASKD" -WOHost localhost >/var/log/
webobjects.log 2>&1 &
Another is to edit
/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/
Resources/Properties
And add
-WOHost localhost
Wotaskd (or the machine :-) needs to be restarted after you do this.
Once we deploy on our public server (with a real host address, not
localhost), I guess there won't be any need to specify WOHost,
will there?
Not if that name is the default name for that server. If there are
multiple names that resolve to the same machine, then you might.
With our current experience and all, we don't want to try it on
our public server, so there's no way for us of knowing if the
problem is actually making it work on a localhost or making it
work at all... We know it's probably just one little thing in our
config, we just can't seem to pinpoint it.
See if the above works. Also you can try
sudo touch /tmp/logWebObjects
and then look at
/tmp/WebObjects.log
to see if the woadaptor has anything useful to say on the matter.
Chuck
_______________________________________________
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]
