Re: Debugging a frozen instance
Re: Debugging a frozen instance
- Subject: Re: Debugging a frozen instance
- From: Mike Schrag <email@hidden>
- Date: Fri, 18 May 2007 16:08:58 -0400
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....
JProfiler can do this, but kill -QUIT will give you a snapshot. 2) I understood that wotaskd would kill and restart a deadlocked unresponsive instance automatically ..... but it did not do it today?
It does not do this ... It will restart a STOPPED instance automatically. But a deadlocked instance is not going anywhere on its own. 3) Besides ERXObjectStoreCoordinator for broadcasting EOF stack changes, what other reliable synchronization options are available?
I have not heard of any of the synchronization options being reliable. It's why I started work on the multicast one, because every other one had a pretty spotty sounding history in the mailing list archives.
However, over the past month or so I have done many 500+ freaking-out-click-crazy-concurrent-user-reading-and-writing load tests on top of the ERX stack synchronizer, both multicast/remote and multistack single-instance without a single deadlock. Anything's possible, but I have not seen it happen under some pretty NASTY conditions.
ms
|
_______________________________________________
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