By default, SpawnOfWotaskd.sh redirects stderr to /dev/null, which is
a really annoying default behavior. Since kill -QUIT writes to
stderr, you won't be able to see this stack trace until you modify
SpawnOfWotaskd.sh (there's a wikibook entry on this somewhere).
On Mar 3, 2007, at 11:44 AM, James Cicenia wrote:
Ok -
Maybe I read that wrong.. however, I ran it.. looked at all my
logs.. and there is nothing!
And, even if I try to force my url to use that instance.. It gets
redirected. This is good
as otherwise my users would scream at me again.
This is a very baffling deployment problem.
- James
On Mar 3, 2007, at 10:23 AM, Mike Schrag wrote:
So I run, as per the wiki: sudo kill -QUIT pid(with the proper
number there).
kill -QUIT will not actually kill a java application. kill -QUIT
causes a dump of all thread stack traces to stderr of the java
process (very useful for debugging). Is there a wiki page that
claims that will exit the application instance? It needs to be
updated if there is.
ms
_______________________________________________
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/james%
40jimijon.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 archive@mail-archive.com
