You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Mainguy, Mike" <MM...@kmart.com> on 2003/11/24 23:29:54 UTC
[OT] RE: DBCP - ReapingObjectPool
Just out of curiosity,
What sort of situation do you have that objects get borrowed, but then
forgotten? This is an interesting side-effect of pooling.
worse is better
-----Original Message-----
From: Dirk Verbeeck [mailto:dirk.verbeeck@pandora.be]
Sent: Monday, November 24, 2003 5:20 PM
To: Jakarta Commons Developers List
Subject: Re: DBCP - ReapingObjectPool
Actually we already have something similar: AbandonedObjectPool.
http://jakarta.apache.org/commons/dbcp/xref/org/apache/commons/dbcp/Abandone
dObjectPool.html
Many enhancements are possible, I have been playing around the java.lang.ref
package to see if it can provide a safe way to recover abandoned objects.
Contributing is as simple as posting your improvements to the list. A whole
new file or a patch for existing files. If there isn't a committer around
then you can also make a bugzilla item for
it. Writing comments to make the review easier helps and if you have junit
tests then you can be sure your contribution won't go unnoticed. If you're
thinking about doing a lot of work then first discuss it on the list
just to make sure we are on the same line.
Contributions are always welcome, bugfixes, enhancements, website updates,
documentation, you name it...
Cheers
Dirk
Juan Ignacio Cidre wrote:
> I was needing an ObjectPool that 'remembers' the borrowed objects so
> it
> can recollect them if not returned after a while.
>
> Is there something like that arround?
>
> I've extended GenericObjectPool to have that functionallity. I can
> give
> it to the project if there is not a better option than mine.
> Since this would be my first contribution to the project, and I don't
> know the customs, I would need some help (I've read all the on-line
> guides, already, )
> N.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
-----------------------------------------
This message and its contents (to include attachments) are the property of Kmart Corporation (Kmart) and may contain confidential and proprietary information. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on information contained herein is strictly prohibited. Unauthorized use of information contained herein may subject you to civil and criminal prosecution and penalties. If you are not the intended recipient, you should delete this message immediately.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [OT] RE: DBCP - ReapingObjectPool
Posted by Juan Ignacio Cidre <ji...@sib.interbanking.com.ar>.
Long story.
I got involved in a big-almost-finished project (arround 6.000 classes,
up to 15 levels of inheritance) 3 months ago to rework the core. It was
having problems. i.e. lost connections and never closed transactions,
concurrency problems, etc.
Replacing the home made ConnectionPool for a good one ;) was easy.
Now I'm dealing with the lost transactions.
In this (again) home-made framework, transaction commiting and closing
is a programmer responsability.
:(
I'm trying to do the same thing here since is exactly the same problem.
finallizers and try{}finally{} has some particular problems in this
framework.
.....
N.
Mainguy, Mike wrote:
>Just out of curiosity,
> What sort of situation do you have that objects get borrowed, but then
>forgotten? This is an interesting side-effect of pooling.
>
>worse is better
>
>-----Original Message-----
>From: Dirk Verbeeck [mailto:dirk.verbeeck@pandora.be]
>Sent: Monday, November 24, 2003 5:20 PM
>To: Jakarta Commons Developers List
>Subject: Re: DBCP - ReapingObjectPool
>
>
>Actually we already have something similar: AbandonedObjectPool.
>http://jakarta.apache.org/commons/dbcp/xref/org/apache/commons/dbcp/Abandone
>dObjectPool.html
>
>Many enhancements are possible, I have been playing around the java.lang.ref
>
>package to see if it can provide a safe way to recover abandoned objects.
>
>Contributing is as simple as posting your improvements to the list. A whole
>new file or a patch for existing files. If there isn't a committer around
>then you can also make a bugzilla item for
>it. Writing comments to make the review easier helps and if you have junit
>tests then you can be sure your contribution won't go unnoticed. If you're
>thinking about doing a lot of work then first discuss it on the list
> just to make sure we are on the same line.
>
>Contributions are always welcome, bugfixes, enhancements, website updates,
>documentation, you name it...
>
>Cheers
>Dirk
>
>
>Juan Ignacio Cidre wrote:
>
>
>>I was needing an ObjectPool that 'remembers' the borrowed objects so
>>it
>>can recollect them if not returned after a while.
>>
>>Is there something like that arround?
>>
>>I've extended GenericObjectPool to have that functionallity. I can
>>give
>>it to the project if there is not a better option than mine.
>>Since this would be my first contribution to the project, and I don't
>>know the customs, I would need some help (I've read all the on-line
>>guides, already, )
>>N.
>>
>>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>-----------------------------------------
>This message and its contents (to include attachments) are the property of Kmart Corporation (Kmart) and may contain confidential and proprietary information. You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on information contained herein is strictly prohibited. Unauthorized use of information contained herein may subject you to civil and criminal prosecution and penalties. If you are not the intended recipient, you should delete this message immediately.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org