Return-Path: Delivered-To: apmail-jakarta-turbine-jcs-user-archive@www.apache.org Received: (qmail 5955 invoked from network); 14 Jan 2005 06:10:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 14 Jan 2005 06:10:25 -0000 Received: (qmail 28831 invoked by uid 500); 14 Jan 2005 06:10:24 -0000 Delivered-To: apmail-jakarta-turbine-jcs-user-archive@jakarta.apache.org Received: (qmail 28673 invoked by uid 500); 14 Jan 2005 06:10:24 -0000 Mailing-List: contact turbine-jcs-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Turbine JCS Users List" Reply-To: "Turbine JCS Users List" Delivered-To: mailing list turbine-jcs-user@jakarta.apache.org Received: (qmail 28655 invoked by uid 99); 14 Jan 2005 06:10:24 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of hanson.char@gmail.com designates 64.233.184.205 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.205) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 13 Jan 2005 22:10:21 -0800 Received: by wproxy.gmail.com with SMTP id 50so91091wri for ; Thu, 13 Jan 2005 22:10:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=RvZ6MTU71AKSnr+y9Oi4qvEeY4+EI+b9XkkJaOexWdfC40ikEBNy+emH4SUokkiwdaKET/8wtVnlUJ/UTtC7yioNgBvWCgFtiqYGgeR9XDzl8hHG6VBAVSEEeDK39LzQPLcXn1gVck/t3L+EtYGjcCzyaTDjzup9/85kULHh9fA= Received: by 10.54.26.65 with SMTP id 65mr261510wrz; Thu, 13 Jan 2005 22:10:19 -0800 (PST) Received: by 10.54.26.6 with HTTP; Thu, 13 Jan 2005 22:10:19 -0800 (PST) Message-ID: Date: Fri, 14 Jan 2005 17:10:19 +1100 From: Hanson Char Reply-To: Hanson Char To: Turbine JCS Users List Subject: Re: Thread deadlock in CacheEventQueue class In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41E40422.5060900@connextra.com> <001101c4f9fc$9ea62560$6401a8c0@smuts> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Or other Concurrent* collections for that matter (ie iteration on an active collection) On Fri, 14 Jan 2005 17:07:01 +1100, Hanson Char wrote: > Ever consider using the jsr166 ConcurrentNavigableMap and > ConcurrentSkipListMap ? > > http://gee.cs.oswego.edu/dl/jsr166/dist/jsr166xdocs/jsr166x/ConcurrentNavigableMap.html > > H > > On Thu, 13 Jan 2005 21:48:05 -0800, Aaron Smuts wrote: > > I suspect that it was the remove / put problem that I solved in 1.1.2. > > It was the only known problem of that sort. It may be due to iteration > > but I thought this was resolved. Iteration is very problematic on an > > active collection. There is no really good way to do it. We basically > > copy the keys in fail fast mode. Were you seeing unrecoverable deadlock > > or just temporary lags? > > > > I'll try some more strenuous testing. The big problem is that it is > > very difficult to create automated tests for the remote and lateral > > caches. I mainly rely on the tester script. I have a random function > > that will beat the hell out of the cache. . . . . > > > > Aaron > > > > > -----Original Message----- > > > From: Matthew Cooke [mailto:matthew@connextra.com] > > > Sent: Tuesday, January 11, 2005 8:52 AM > > > To: turbine-jcs-user@jakarta.apache.org > > > Subject: RE: Thread deadlock in CacheEventQueue class > > > > > > We had major problems when we used the remotecache configuration in > > push > > > mode rather than delete mode (removeOnPut). > > > > > > At the time we strongly suspected a deadlock caused by the local puts > > > placing cached items back into the local memory caches when they > > > recieved async put events from the remotecache. > > > > > > Could the deadlock we were seeing when using remotePuts have been the > > > same thing? We are quite keen to try remotePuts again as this > > > functionality would be very useful to us (would allow iteration over > > > whole caches on individual machines). As the deadlock was only > > occuring > > > under high load we don't have a reliable way to test. > > > > > > Any advice appreciated! > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > turbine-jcs-user-unsubscribe@jakarta.apache.org > > > For additional commands, e-mail: > > turbine-jcs-user-help@jakarta.apache.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org