> -----Original Message----- > From: Juozas Baliuka [mailto:[EMAIL PROTECTED] > Sent: 23 July 2003 12:52 > To: Jakarta Commons Developers List > Subject: Re: [DBCP] AbandonedTrace - Connection Recovery > > Logging is useless in this case,
Such a statement seems ludicrous.... The relative merits of including support for recovery of connections or not aside; The logging of cases where poor coding/design/external libraries leaks an expensive resource with no impact to normal usage is IMHO an always useful feature... > it is not a problem if it doe's not inspire crap like "autorecovery", > but it was a mistake too and this dicussion proves it, does not it ? I'm sorry if I'm interpreting this wrong but are you implying that the facility which logs such events occuring would encourage the use of maladaptive recovery strategies long term rather than fixing the problem at source? his is somewhat like saying an error report from a Junit test encourages people to stop unit testing... Attempting to return to the original topic I would very much like the functionality described above for finalized connections available in the official DBCP project, if this is by an Observer or Strategy plugin all the better. Matt ************************************************************************** The information transmitted herewith is sensitive information intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
