I tried just turning DirectConnect off, and I can't connect to the
instance (as Guido intimated). I am on Leopard, but am using WO5.3,
and I have WOHost=localhost in my wotaskd properties file.
I then tried setting the port to a specific number (11351) with
DirectConnect off, but the browser still came up specifying port 80
and didn't connect to my app instance. I then turned DirectConnect
back on and my app came up on the specified port. However, with
DirectConnect on, when I specify port 80 I get an error on launch that
the port is already in use. I do have web sharing turned off. So, in
the end I still can't bring my app up on port 80 to test my cookie
code. Anything I missed trying?
Thanks,
Jeff
On Jan 7, 2008, at 2:01 PM, Chuck Hill wrote:
On Jan 7, 2008, at 11:30 AM, Guido Neitzer wrote:
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). ;-)
Grin. Yeah, that probably won't be your problem.
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.
It sounds like maybe the adaptor is caching the wotaskd config.
Hmmm, yes.
# The apache module gets its configuration from the wotaskds
# listed on the configuration line
# For multiple hosts:
# WebObjectsConfig http://<name-of-a-host>:<port-on-a-host>,http://
<name-of-another-host>:<port-on-a-host> <interval>
# For localhost:
WebObjectsConfig http://localhost:1085 10
I think that means it checks for an update to the config every 10
seconds.
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.
I will guess that it is finding the configuration from a previous
launch, as the port number has not changed, this still works.
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.
How long is while, about 10 seconds?
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.
Agreed, not a good situation.
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?
Two files? Which two files?
Chuck
--
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-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/jeffandmonica%40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
