Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of rene.glanzer@gmail.com
 designates 209.85.218.213 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;
        b=quNSm41OgZHIfWISLeDTf2aurP0bypzDb7ebM94lERODqEsF00/PvEJA5713s8lFhP
         KX+aJfKqsXpHpI8FiKbsf0dYBOHWqpR4foJ22LmddCX8NVaYvmv0H6Yr7jTsOKquLKjD
         2zIWHtZWOE+Q/jE2GQpVOfJsaPgJ6cpy4J3kc=
MIME-Version: 1.0
In-Reply-To: <f2e8eedf0906170723k4e99e7dbv93184c3e6ced6b9d@mail.gmail.com>
References: <4fc6b7820906090933tf707810xce8470c2614784cd@mail.gmail.com>
	 <139558.17721.qm@web50302.mail.re2.yahoo.com>
	 <4fc6b7820906170047i6b383a0s7929591a6408db61@mail.gmail.com>
	 <h1ad67$d7$1@ger.gmane.org>
	 <4fc6b7820906170248j7951deejc4503a9d20e59e86@mail.gmail.com>
	 <h1aejc$3m0$1@ger.gmane.org>
	 <4fc6b7820906170427r1e984235w1dac6b87c1d5fb98@mail.gmail.com>
	 <4fc6b7820906170707y5201c9bbp58861b42d0648fb4@mail.gmail.com>
	 <327858f40906170717y4aa6664o23217c887f517c42@mail.gmail.com>
	 <f2e8eedf0906170723k4e99e7dbv93184c3e6ced6b9d@mail.gmail.com>
Date: Wed, 17 Jun 2009 16:30:35 +0200
Message-ID: <4fc6b7820906170730v5a2ac91fl4b99135ffaa292e0@mail.gmail.com>
Subject: Re: [collections] LRUMap Problem ConcurrentModificationException
From: =?ISO-8859-1?Q?Ren=E8_Glanzer?= <rene.glanzer@gmail.com>
To: Commons Users List <user@commons.apache.org>
Content-Type: multipart/alternative; boundary=001485f794706eae79046c8c224b

--001485f794706eae79046c8c224b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I was searching for a very lighweight cache systems with not much overhead
for my purposes. The LRUMap just matched
perfectly except the little iterator problem.


2009/6/17 James Carman <james@carmanconsulting.com>

> Or, ehcache or oscache or something like that?
>
> On Wed, Jun 17, 2009 at 10:17 AM, Leon
> Rosenberg<rosenberg.leon@googlemail.com> wrote:
> > why don't you just use softreference + expiration timestamp and save
> > all the trouble?
> > Leon
> >
> > On Wed, Jun 17, 2009 at 4:07 PM, Ren=E8 Glanzer<rene.glanzer@gmail.com>
> wrote:
> >> Hi,
> >>
> >> it's me again with an update.
> >> the LRUMap.mapIterator() still produces the
> >> ConcurrentModificationException when a call to MapIterator.remove()
> >> occurs.
> >>
> >> Maybe this info helps
> >> Ren=E9
> >>
> >>
> >> 2009/6/17 Ren=E8 Glanzer <rene.glanzer@gmail.com>:
> >>> Hi J=F6rg,
> >>>
> >>> it's me again. With a smile on my face :-)
> >>>
> >>> I changed my code according to your hint.
> >>> Now i don't use the keySet but the entrySet. With only to adopt the
> rest of
> >>> the method to the entrySet and still
> >>> calling the remove() method of the iterator in my tests no
> >>> ConcurrentModificationException occured!!
> >>>
> >>> Additionally now I'm using the LURMap.mapIterator() which also perfor=
ms
> well
> >>> and according to the docu should be prefered over the entrySet or
> keySet.
> >>>
> >>> Now the new an well working code looks like this:
> >>>
> >>> public void removeAllExpiredItems()
> >>>   {
> >>>     synchronized(this.store)
> >>>     {
> >>>       MapIterator it=3Dthis.store.mapIterator(); //Here I'm using the=
 new
> >>> MapIterator
> >>>       while(it.hasNext())
> >>>       {
> >>>         m_catLog.debug("Reading object");
> >>>         Object key=3Dit.next();
> >>>         Item currentItem=3D(Item)it.getValue();
> >>>         if(currentItem.birth=3D=3D0)
> >>>         {
> >>>           m_catLog.debug("0 birth found for key "+key+" calling
> >>> Iterator.remove");
> >>>           it.remove();
> >>>         }
> >>>       }
> >>>       this.setLastCleanDate(new Date());
> >>>     }
> >>>   }
> >>>
> >>> Thousand Thanks for your help J=F6rg
> >>> this fixed my Problem and maybe also fixes the problems from the othe=
r
> >>> people who suffered the same problem.
> >>> Furthermore I'm pleased to see that the JIRA issue COLLECTION-330 is
> >>> handling the problem with the keySet call.
> >>>
> >>> 2009/6/17 J=F6rg Schaible <joerg.schaible@gmx.de>
> >>>>
> >>>> Ren=E8 Glanzer wrote at Mittwoch, 17. Juni 2009 11:48:
> >>>>
> >>>> > Hi J=F6rg,
> >>>> >
> >>>> > that are great news, I'll give it a try.
> >>>> > And of course I'll report my experience.
> >>>>
> >>>> That would be fine. Actually I opened an own JIRA issue for this now
> >>>> (COLLECTION-330), COLLECTION-3 was simply too vague and had a too lo=
ng
> >>>> history of different symptoms.
> >>>>
> >>>> - J=F6rg
> >>>>
> >>>>
> >>>> --------------------------------------------------------------------=
-
> >>>> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> >>>> For additional commands, e-mail: user-help@commons.apache.org
> >>>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: user-help@commons.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> > For additional commands, e-mail: user-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>

--001485f794706eae79046c8c224b--