commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Delfosse Julien <>
Subject RE: GenericKeyedObjectPool synchronization
Date Fri, 23 Apr 2004 06:12:23 GMT
Thanks for your response.

I was actually planning to use a bunch of generic object pool objects (one
for each key) and to synchronize on that particular pool, but I guess it
would be a waste of space.  Other possibility include using the
util.concurrent package and semaphores, but I have to be extra-carefull
about deadlocks, resource leaks and other boring (and complicated) stuff.

I'll definitely check your GenericObjectPool synchronization.  Is it in the
1.1 distro or do I have to browse the cvs head (or a specific branch ?)

Thanks again


-----Original Message-----
From: Dirk Verbeeck [] 
Sent: Thursday, April 22, 2004 20:55
To: Jakarta Commons Users List
Subject: Re: GenericKeyedObjectPool synchronization

If I had such implementation then I would have committed it ;-)

The currect GenericKeyedObjectPool could be patched to unsynchonize 
the method just like I did with GenericObjectPool. I don't have much 
time right now but I can always help review/fix.

-- Dirk

Delfosse Julien wrote:

> Hi,
> first of all, thanks for making these kewl components available, these are
> really helpfull.
> I have to manage a pool of objects (documentum sessions) that will be
> (using the user principal as key)
> I have noticed that the borrowObject method of the GenericKeyedObjectPool
> synchronized and that will cause unacceptable performance problems on our
> applications, since we manage a big number of concurrent users,
> would definitely be a bottle neck.
> Is anyone aware of an implementation of KeyedObjectPool that allows
> concurrent access to the borrowObject method ?
> Thanks in advance.
> Julien Delfosse

To unsubscribe, e-mail:
For additional commands, e-mail:

Legal Notice: This electronic mail and its attachments are intended solely
for the person(s) to whom they are addressed and contain information which
is confidential or otherwise protected from disclosure, except for the
purpose they are intended to. Dissemination, distribution, or reproduction
by anyone other than their intended recipients is prohibited and may be
illegal. If you are not an intended recipient, please immediately inform the
sender and send him/her back the present e-mail and its attachments and
destroy any copies which may be in your possession. 

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message