Implement an optional tracing mechanism in jdbc-ng
--------------------------------------------------
Key: GEOT-2131
URL: http://jira.codehaus.org/browse/GEOT-2131
Project: GeoTools
Issue Type: New Feature
Components: data jdbc-ng
Affects Versions: 2.5.1
Reporter: Andrea Aime
Assignee: Andrea Aime
Priority: Critical
Fix For: 2.5.2
Implementing a tracing mechanism that allows to discover where the connection
pools or connections that are being lost were grabbed.
Implementation wise, have a system variable that enables the creation of Trace
objects when the datastore or the connection holder is created, and that dumps
it on finalize if the connection wasn't closed/the pool wasn't freed.
This should significantly easy up chasing for code that grabs critical
resources and does not clean them up properly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
