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 [EMAIL PROTECTED] 2003-03-24 16:26 ------- This is not true, if the pool has a function which automatically puts a connection back into the pool. This is, what this pool call an "abandoned" connection if an application do not pass back the connection back within an specified time. Since not all programmers are perferct and not all programms are perfect, this is a nice feature to prevent an db connection leak. But, if the connection is passed back to the pool, the object passed to the application should never ever be valid. What, if the wrongly programmed thread which connection is passed back to the pool, issues a "commit" while another thread is in the middle of an transaction? To the performance problem: If one uses abandoned connections, he/she has to live with this performance gain. If i had a web application in mind, such get/release is not very often and performance might not be a problem. Inconsistent Data is for sure a great problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
