Re: Can't retrieve cookies
Re: Can't retrieve cookies
- Subject: Re: Can't retrieve cookies
- From: Chuck Hill <email@hidden>
- Date: Mon, 7 Jan 2008 20:27:46 -0800
On Jan 7, 2008, at 2:54 PM, Guido Neitzer wrote:
On 07.01.2008, at 13:01, Chuck Hill wrote:
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.
Yep. I figured that much even with a Workspace with just a Hello
World in it. ;-)
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.
The weird thing is, that it works on that G4 all the time with a
fixed port even for the first application start after a reboot.
And that is with WO 5.4?
What I really find is weird is: I have started two instances one
after the other with stopping the first one before starting the
second and even after about a minute wotaskd still shows that it
knows about the instances - after a little bit longer they are
gone. I don't want to do stopwatch checking here, so be it "a while".
Both of them came up in the browser with "The requested application
was not found ...", later they showed up.
But when I set the app to be on a port different from -1 it shows
up in wotaskd immediately, WOPort set to -1 shows up after a couple
of seconds (I guess depending on where inside the 10 second
interval the app shows up). Maybe something is going wrong in the
communication there.
But that doesn't explain why we had trouble with some machines /
projects where it worked for some requests and didn't work like
about every third click or so. That was REALLY weird.
I have not seen that for a while.
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.
See above - it worked fine even for a freshly rebooted machine.
Have to do some testing tonight again to figure out more of that.
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?
Depends. It seemed to be less then 10 seconds so your guess might
be right. But why was that working all the time with WO 5.3 on
Tiger? Was the setup different there? I can't really check at the
moment.
I don't have even a bad guess at that.
What is the idea of having to touch TWO files to actually get log
output?
Two files? Which two files?
I had to touch the actual logfile and "/tmp/logWebObjects" (the
second as root) to get any output. Is that a security thing or what
reasoning is behind touching the second file?
I have never had to do anything other than sudo touch /tmp/
logWebObjects. But that is on 5.3.
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden