On Aug 18, 2006, at 1:14 PM, Sacha Michel Mallais wrote:
On Aug 18, 2006, at 1:03 PM, Jonathan Miller wrote:
Mysteriously, one of the two applications running on my server
started to hiccup and then finally quit today.
I'm running OS X 10.4.7 on XServe
I'm getting the following error in the log file:
Info: <WebObjects Apache Module> new request: /cgi-bin/WebObjects/
Debug: App Name: vxAdmin.woa/wa/default (7)
Info: V4 URL: /cgi-bin/WebObjects/vxAdmin.woa/wa/default
Info: tr_selectInstance(): scheduler failed to select instance.
Error: Request handling error: The requested application was not
found on this server.
In WebObjects Monitor it shows that the instance was started but I
cannot connect to it either through apache or directly.
Is there any chance you have accidentally renamed the application
and are using an old URL? Another option is to try restarting
wotaskd, since it appears that wotaskd can both see (Monitor) and
not see (log extract) your app.
That app may also be deadlocked. This is a particular problem if it
is not dispatching requests concurrently.
Another weird symptom is the only way to stop the application is
to delete the instance ( I saw someone else had a similar issue).
Does anyone have a solution?
This happens more often than WO developers would like to admit.
Deleting the instance is not the recommended way to stop an app
that isn't stopping from Monitor. Instead, use the command line:
lsof/ps and kill (search the archives for exactly how to use those).
There is also a Force Quit option on the configuration page for each
individual instance. That can save you a trip to the command line.
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden