|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Sebastien Alborini
|Sent: Wednesday, October 18, 2000 9:38 AM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] Memory leak in cache
|
|
|Hi,
|
|With these 2 changes (the bug in demote, and the memory leak fix), I am
|happy to announce that the new cache performed at least as well as the
|old one (in terms of memory): 100 parallel client threads working on
|50000 entity beans, and the java heap is stable (6.7M) !!
I thought it was 150,000?
marc
|
|Moving to the next test: locking problems with concurrent client threads
|accessing the same bean...
|
|Sebastien
|
|
|
|
|"Bordet, Simone" wrote:
|>
|> Hey Sebastien,
|>
|> > Hi,
|> >
|> > There is a memory leak in EnterpriseInstanceCache: m_lockMap
|> > only grows,
|> > after 10 minutes I have 10000 CacheKeys and mutexes in memory.
|> >
|> > I think we should remove the id/mutex association once the
|> > bean has been
|> > passivated. Maybe call removeLock(id) around
|> > EnterpriseInstanceCache:385?
|>
|> Yes, as you suggested it'll read:
|>
|> ...
|> passivate(ctx);
|> executed();
|> removeLock(id);
|> freeContext(ctx);
|> ...
|>
|> Thanks,
|>
|> Simon
|
|
