Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jeff.ramsdale@gmail.com
 designates 209.85.213.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=qq+VYdn9ejo/pB56rvv1JQHU2ru87hdpV6SeTgavfk0Ls4LkVFlORojto6Lt3Zb+tx
         okF5gIC9q6dh8uSYq+wFDJQGSd51f7j6u6pZuDaGdH9G/8lj8zJ5ZaR30sYWwTBuvzk4
         GAPnnEka3LxupHHjQohjJwb9HRtXbbhVSJZB4=
MIME-Version: 1.0
In-Reply-To: 
 <DE2C5331EF5E0646B3E4687750E3A9F84876F63D9F@IE2RD2XVS041.red002.local>
References: <4CF89BD3.3030103@acm.org>
	<DE2C5331EF5E0646B3E4687750E3A9F84876F63D9F@IE2RD2XVS041.red002.local>
Date: Sat, 4 Dec 2010 17:51:38 -0800
Message-ID: <AANLkTikx2Vasa=Q+56oX3tG+mv-pLxao8=fzZ1k=kL0Y@mail.gmail.com>
Subject: Re: Progress, and a problem
From: Jeff Ramsdale <jeff.ramsdale@gmail.com>
To: river-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Shay, as Patricia has clearly stated in the past she's doing this as a
hobby, not looking for a production system. I'd rather see you get
involved in the community than try to draw people away. Free is great
(as is non-free--I have nothing against commerce), but Apache River is
open source. How will you contribute?

-jeff

On Sat, Dec 4, 2010 at 11:57 AM, Shay Hassidim <shay@gigaspaces.com> wrote:
> Patricia,
> I suggest you to try the GigaSpaces implementation. =A0We solved this iss=
ue long time ago.
> We have a free community edition, so you can download it and use it in pr=
oduction.
> Take a look also on our exclusive locking option. You might find it usefu=
l.
> Shay
>
> ----- Original Message -----
> From: Patricia Shanahan <pats@acm.org>
> To: river-dev@incubator.apache.org <river-dev@incubator.apache.org>
> Sent: Thu Dec 02 23:27:15 2010
> Subject: Progress, and a problem
>
> I'm currently hunting an intermittent bug found by the test
> qa/src/com/sun/jini/test/impl/outrigger/matching/StressTestWithShutdown.t=
d
>
> After a failure on Hudson, I modified the .td file to make it fail more
> often by increasing the number of entries (10,000), readers (1000), and
> writers (1000).
>
> The writers write entries in an OutriggerServerImpl JavaSpace. The
> readers read, and then take, entries that the writers wrote. Sometimes,
> a reader fails to find an entry a writer claims to have written, causing
> a timeout.
>
> The outrigger implementation depends on the class FastList which seems
> to use the infamous Double Checked Locking idiom
> (http://www.cs.umd.edu/~pugh/java/memoryModel/DoubleCheckedLocking.html)
>
> The good news is that any memory model related error in FastList, or the
> related class EntryHolder, would be a plausible cause of the observed
> symptom. The bad news is that FastList and EntryHolder seem to have been
> written to be very aggressively parallel, possibly by someone who was
> only familiar with sequentially consistent memory. :-(
>
> Usually, it is easy to fix a problem once it has been located. This may
> be a bit more difficult, especially because I assume the parallelism is
> needed for acceptable JavaSpace performance.
>
> Patricia
>
>
>