David Koski wrote:
> Eric Hermanson wrote:
> > - Monitor starts up all 12 applications that are configured to
> > auto-start/auto-recover (verified by looking at process list), however,
> > not all applications show up in /Temp/WebObjects.conf
>
> We noticed some behavior like this too, and it is not actually related to
> monitor (the apps themselves write this file out when they start). It looks
> like there is a race condition here on a non protected resource -- they all
> start and the same time and clobber the file.
When running an app from the Monitor, this file in TEMP is not even
used. The WOAdaptor uses the entry the Monitor writes into the public
conf file.
>
> > - Monitor itself is running (and configured properly as a service),
> > but when you try to hit it you get the following error: "The requested
> > application was not found on this server"
>
> I wonder if this is due to the wrecking of the /temp/WebObjects.conf file?
> Is it listed in there when it does this?
Possible since the Monitor never writes a entry for itself in the public
conf file, the only way the WOAdaptor can find it is if there is a valid
entry in the TEMP conf file. If as a service the Monitor app doesn't
write to this successfully OR somehow the entry gets invalidated
somehow, then there would be no way to connect UNLESS you use
DirectConnect and bypass the web server. Hence it is a good idea to
default write the port number you wish the Monitor to listen on...
defaults write Monitor WOPort 3333
d
