From: Godmar Back (gback@cs.utah.edu)
Date: Thu Feb 04 1999 - 14:37:53 EST
That's the patch I meant:
Forwarded message:
> From kaffe@rufus.w3.org Thu Feb 4 12:35:47 1999
> Resent-From: kaffe@rufus.w3.org
> Resent-Date: Thu, 4 Feb 1999 14:35:36 -0500
> Resent-Message-Id: <199902041935.OAA12327@rpmfind.net>
> X-Authentication-Warning: neon.cs.umn.edu: dejong owned process doing -bs
> Date: Thu, 4 Feb 1999 13:35:23 -0600
> From: Moses DeJong <dejong@cs.umn.edu>
> To: kaffe@rufus.w3.org
> Subject: Re: Hashtable patch, more serialization patches
> In-Reply-To: <36B9DC99.84A701F2@di.uminho.pt>
> Message-ID: <Pine.SGI.4.05.9902041332100.20594-100000@neon.cs.umn.edu>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Sender: owner-kaffe@rufus.w3.org
> Precedence: bulk
> Reply-To: kaffe@rufus.w3.org
> Errors-To: kaffe-error@rufus.w3.org
> X-loop: kaffe@rufus.w3.org
> X-mailing-list: kaffe@rufus.w3.org
>
> On Thu, 4 Feb 1999, Jose Orlando Pereira wrote:
>
> >
> > Hi,
> >
> > There seems to be a bug in java.lang.Hashtable that is triggered when,
> > after being used for a while, all free slots are marked as "removed".
> > The first patch below corrects this problem.
>
> That patch worked great! I was getting the "Inconsistent Hashtable"
> exception too. You patch solved my problem.
>
> mo dejong
> dejong at cs.mn.edu
>
>
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:58 EDT