>> You could also see it from a different point: some part of your code is >> misbehaving (ie not releasing connections back to the pool in a timely > > Interesting. I would say why your code isn't going to be fixed in > first place? And should the library offer tools for this in first > place? >
If you don't have the handle of the faulty connection (i.e., it might be part of a third party library) then you won't be able to nuke it. But that's a corner use case. I'd rather have some helpers to identify *where* the connections and/or transaction have been opened. Coincidentally, right now I'm trying to fix a bug in our code regarding zombies opened connections and whatever you add to API that help us find these would be great. Regards, Hernán Martínez-Foffani ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
