Re: Temporarily deaf instances
Re: Temporarily deaf instances
- Subject: Re: Temporarily deaf instances
- From: Gary Teter <email@hidden>
- Date: Mon, 24 Mar 2008 12:18:18 -0700
This is the new one with JGroups swapped out for JMS.
We tried a TON of different configurations for jgroups and just
couldn't get it running reliably, including using JMS as a transport
for jgroups.
On Mar 24, 2008, at 12:08 PM, Mike Schrag wrote:
We're using an ERXRemoteSynchronizer-derived change notification
system over JMS (openjms-0.7.7-beta-1 running on a different box)
Is this the old JMS remote synchronizer or the new one with JGroups
sending on top of JMS? The old Wonder JMS synchronizer is known
(from anecdotal reports) to have deadlock problems. Regardless,
though, you would see a hung EO stack in your stack dumps (and it
would never come back). It doesn't make sense to me that kill -
QUIT is blocked -- that implies to me that it's something much
lower-level. But you're not getting CPU starvation, because you're
only running at like 2.4% ..... Just thinking out loud here.
ms
--
WireHose: Smart metadata and personalization for WebObjects.
http://wirehose.com/
_______________________________________________
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