commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17677] - Pooled connection architecture vulnerable to double use
Date Mon, 24 Mar 2003 15:27:21 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17677>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17677

Pooled connection architecture vulnerable to double use





------- Additional Comments From dgraham@apache.org  2003-03-24 15:27 -------
"Because the same wrapper 


class instance is handed out multiple times, it makes it possible for 


inadvertent sharing to occur."  This is exactly the way a pool should work so I 
don't believe this is an architectural flaw.  Client code using the pool is 
responsible for not sharing objects retrieved from the pool and returning them 
to the pool ASAP.  Creating new wrapper objects on each request would lead to 
performance degredation.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message