Hi Cara,
On Jul 21, 2006, at 4:07 AM, Cara MacNish wrote:
Thanks very much for the replies.
On 20/07/2006, at 10:10 PM, Georg Tuparev wrote:
We use 10.4.7. but we do not experience these problems... so look
somewhere else...
It may not be 10.4.7 "as such", but I'm pretty sure its something
thats at least been changed by the (combo) upgrade. It worked fine
before I did it.
Are there multiple network interfaces and / or IP addresses
associated with this machine?
On 20/07/2006, at 11:36 PM, Graham J Lee wrote:
[2006-07-20 17:55:09 WST] <main> A fatal exception occurred:
InetAddress bytes need to have 4 (or better) 6 bytes:
<WOApplication>: Cannot be initialized.
I've seen that error exactly once, on a box which hadn't picked up
an IPv4 address so WO was binding to its IPv6 address...might
turning off IPv6 explicitly sort that out?
Thanks. I've tried that but it made no difference.
I have seen that error occasionally, but never two launches in a row
that I recall.
However, I do think it could be network related in some way. I've
now tried running it from the command line, and it works as long as
I explicitly include the port number (2001 in http://
gungurru.csse.uwa.edu.au:2001/cgi-bin/WebObjects/huygensWS.woa). If
I don't include it it says the requested application was not found
on this server, and in the log it writes:
Info: <WebObjects Apache Module> new request: /cgi-bin/WebObjects/
huygensWS.woa/wa/default
Debug: App Name: huygensWS.woa/wa/default (9)
Info: V4 URL: /cgi-bin/WebObjects/huygensWS.woa/wa/default
Info: tr_selectInstance(): scheduler failed to select instance.
Error: Request handling error: The requested application was not
found on this server.
That is normal for an instance started from the command line.
Presumably when an instance is started in the monitor (assuming it
works) it glues in the necessary translations from the generic
address?
Yes.
Note that I pasted the arguments directly from the setup in the
monitor to the command line - so they are the same.
Those are not all that is passed to the application, only your
additions to the standard values. If you look at the configuration
for a single instance (not the application wide one), below where is
says, "With the current settings, this instance will be started with
the following arguments:" you can call all that is passed to that
particular instance on startup.
Note also that the monitor won't stop an instance either. The only
way to stop the switch cycling down is to delete the instance.
Can anyone offer any hints as to why the woa would deploy from the
command line, but not from monitor with the same arguments?
The number one reason is permissions. Unless you are launching the
app from the command line as appserver, the launching user is
different when JavaMonitor (wotaskd actually) launches an
application. See http://www.gvcsitemaker.com/gvc.webobjects/
faq&mode=single&recordID=19193&nextMode=list
The inability of JavaMonitor to start / stop instances may also
reflect wotaskd getting launched with a different name than that used
in the Hosts section in JavaMonitor. You can add a line like
-WOHost ungurru.csse.uwa.edu.au
in /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/
Resources/Properties to force it to launch under a specific host name.
Chuck
--
Coming sometime... - an introduction to web applications using
WebObjects and Xcode http://www.global-village.net/wointro
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/products/practical_webobjects
_______________________________________________
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]
