On 07.01.2008, at 12:10, Chuck Hill wrote:
I think that is a networking issue. Art (or someone) posted this a
while back:
I think that was the problem with webobjects starting too early or too
fast in the boot process. This won't happen on my test machine (dual
G4 867MHz). ;-)
Does yours have that?
Yes, it is in there. I'm on Leopard, using WO 5.4 for testing /
writing some stuff and WO 5.3 for production work. It happens on both
systems so I think it is either the Adaptor or wotaskd.
Launching both wotaskd and the app with -WOHost localhost has always
fixed these sorts of problems for me. Does this no longer work on
5.4?
Not for me. I will give it a try tonight again with this setting. What
solved the problem on my test machine was setting a specific port. For
random port, always the first access failed, when I reload a couple of
times, it works eventually, or if I wait for a while - than it works
too.
I always do that too, mostly so I can make bookmarks.
Yeah, but if you run into that problem with a "clean" machine (just
installed) and a Hello World program - this is real shit as it
frustrates beginners to no end.
And it's pain in the *beeep* to get log output from the WO
Adaptor ... :-(
Worse in 5.4?
I actually never tried on Tiger ... ;-)
What is the idea of having to touch TWO files to actually get log
output?
cug, out for lunch now
--
http://www.event-s.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
