Re: Debugging a frozen instance
Re: Debugging a frozen instance
- Subject: Re: Debugging a frozen instance
- From: Chuck Hill <email@hidden>
- Date: Fri, 18 May 2007 12:53:44 -0700
On May 18, 2007, at 12:46 PM, Kieran Kelleher wrote:
Hi List,
A few questions ......
1) Has java 5 given us any new way to attach to a running app and
see the threads or does the foresight of applying jdb startup
parameters to each instance still apply with a view to using jdb
*if* you get a frozen app as outlined in WO wiki....
http://en.wikibooks.org/wiki/Programming:WebObjects/
Web_Applications/Deployment/Debugging_Frozen_Deployed_Instances
You mean besides sending it a kill -QUIT signal?
2) I understood that wotaskd would kill and restart a deadlocked
unresponsive instance automatically ..... but it did not do it today?
It has never done that for me.
3) Besides ERXObjectStoreCoordinator for broadcasting EOF stack
changes, what other reliable synchronization options are available?
Just variations of that one, AFAIK.
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