Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 64151 invoked from network); 3 Apr 2009 09:56:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Apr 2009 09:56:09 -0000 Received: (qmail 41158 invoked by uid 500); 3 Apr 2009 09:56:09 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 41079 invoked by uid 500); 3 Apr 2009 09:56:09 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 41069 invoked by uid 99); 3 Apr 2009 09:56:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 09:56:09 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates 209.85.219.180 as permitted sender) Received: from [209.85.219.180] (HELO mail-ew0-f180.google.com) (209.85.219.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 09:55:59 +0000 Received: by ewy28 with SMTP id 28so937525ewy.25 for ; Fri, 03 Apr 2009 02:55:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=fBNOmyfKUgsRoWy2rIAgD34hUETwJMeItKonYsAdL3I=; b=CjBBHZ8thoquCsxddozHPXynFirJEqeoEfYiiiiUkhw2ip3/+b5gqlhAAQzCLEoaJV yf/7Sn67g+cnPSSHOc5HK5dHmXEDGo8V5PxOUY76QfM/TSRwsCcy53CSjvjtCS8sYA/Z PX3v9W2akHHB8Be2K7Il0RduRzo0c0ngZv4G8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=F69EHALlwymqR83j+jvjrPUYww4qn8IJ+RUb96k72Gm6d1ZLQae4v7NGT2pKixBnuz kHclVelUAhXs6lGUkItJBnNYmx5KQwzgG2+n8VBxeUe5ccA4bfY9hrzRq+cQzbedpihP /w4zOyVvBXyE9ETObLFd9FkjTaaOg8gaGDf6o= Received: by 10.216.49.194 with SMTP id x44mr344728web.130.1238752539417; Fri, 03 Apr 2009 02:55:39 -0700 (PDT) Received: from ?192.168.0.2? (lon92-10-78-226-4-211.fbx.proxad.net [78.226.4.211]) by mx.google.com with ESMTPS id g9sm4613795gvc.4.2009.04.03.02.55.38 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 03 Apr 2009 02:55:38 -0700 (PDT) Sender: Emmanuel Lecharny Message-ID: <49D5DD1A.1070303@nextury.com> Date: Fri, 03 Apr 2009 11:55:38 +0200 From: Emmanuel Lecharny User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: [ApacheDS] OutOfMemoryError References: <49CA64C6.10808@planetquake.com> <49CA78E2.4030304@planetquake.com> <5A2110DC1CD00B45A0832E5BF98ECB0602CFB24DEB@ex2> <49D209C4.8040107@nextury.com> <5A2110DC1CD00B45A0832E5BF98ECB0602CFB24EDA@ex2> <49D4EF06.4090500@nextury.com> <49D5DBCD.7000806@planetquake.com> In-Reply-To: <49D5DBCD.7000806@planetquake.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Martin Alderson wrote: > Hi Emmanuel, > >> There is a BIG bug in MINA 2.0.0-M4 I fixed last week : the >> CircularList is not thread safe, and when writing messages into it, >> you may have impredictable results. I replaced it with a >> ConcurrentList, and the problem is now fixed. We still have to >> release MINA 2.0.0-RC1, but I think we will do maybe next week. >> >> Can you do that : build MINA trunk, and use it >> (MINA-2.0.0-M4-SNAPSHOT) for a new test, to see if the >> SearchResponseEntry are still hold ? >> >> Thanks ! > > I've just built mina trunk (producing > mina-core-2.0.0-RC1-SNAPSHOT.jar) and tested with that. > > Unfortunately it still does the same, i.e. the SearchResponseEntrys > are held by the DefaultWriteRequestQueue. Ok, so we still have a serious issu we have to fix quickly... Can you give us the information about the used JVM, memory used and such so that we can reproduce the problem easilly ? May be we should reopen the JIRA too. Thanks ! -- -- cordialement, regards, Emmanuel L�charny www.iktek.com directory.apache.org