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.
On 21/07/2006, at 12:40 AM, Asa Hardcastle wrote:
One note, we're not using java 1.5 yet, I keep ignoring the
download. Is anyone out there running WO 5.3 in 1.5?
Yes, I upgraded to 1.5 when Apple up-rated it to the default for
Xcode. Its been working fine.
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.
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.
Presumably when an instance is started in the monitor (assuming it
works) it glues in the necessary translations from the generic address?
Note that I pasted the arguments directly from the setup in the
monitor to the command line - so they are the same.
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?
Thanks muchly
Cara
On Jul 20, 2006, at 2:01 PM, Cara MacNish wrote:
I (foolishly) did the MacOS 10.4.7 upgrade on my server this
afternoon, and it has broken my webobjects deployment big time.
When I start an instance in the monitor the Frankenstein switch
thing keeps cycling up forever. Furthermore (which I haven't seen
before) when I hit "stop" it just cycles down forever.
_______________________________________________
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]
