That's what everyone says, but JGroups made this particular problem
worse. :(
Hmm .. I've been running the JGroups version for almost two years in
production and with some pretty substantial load tests (500-1000
insane-clicky-concurrent-making-changing users). I've never run it on
top of JMS, and admittedly, you lose persistent message delivery with
the non-JMS one, but for us this wasn't a problem.
But still, I don't think this is a deadlock because you come back, and
you don't come back from deadlocks. JGroups does love to create
threads, but they don't have many live concurrently, generally (just
lots created over time). Without being able to get a thread dump, it
will be pretty hard to diagnose this. If you're running on 1.5 (I
think you must be because I think JGroups is 1.5 only?) you might try
running a jstack on your app when this happens, though I would think
it would have less success than a kill -QUIT would ... Worth a shot,
though.
ms
_______________________________________________
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]
