On 07/08/2009, at 2:44 PM, Chuck Hill wrote:
Grumble. It used to be that you could edit SpawnOfWotaskd.sh, and then do a "kill -QUIT <pid>" on your application to get a thread dump. On Leopard Server, this does not seem to produce any output. It still works for applications running in Eclipse. I am not sure yet if this is a Client vs Server issue or a Development vs Deployment issue. At first I thought it was just one machine, but I have reproduced this on a different machine now. If I run the app from the command line, I can set the thread dump. That suggests the problem lies in wotaskd launched processes.
Monitor remote apps + grab thread dumps via visualvm (I think you need JDK 1.6)
https://visualvm.dev.java.net/docindex.html Apparently works on all platforms: http://www.adaptj.com/main/stacktrace
Has anyone else noticed this? Any solutions? I know about jstack but, sigh, it is also defective on Leopard (or is that Apple's Java 1.5?) in that it can't print the correct thread names.
Seems strange. with regards, -- Lachlan Deck _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
