do not cache SeLayer and SeTables since they hold a reference to a connection
------------------------------------------------------------------------------
Key: GEOT-810
URL: http://jira.codehaus.org/browse/GEOT-810
Project: GeoTools
Type: Improvement
Components: arcsde
Versions: 2.2-RC0
Reporter: Gabriel Roldán
Assigned to: Gabriel Roldán
Fix For: 2.3.M0
in ArcSDEConnectionPool we maintain a cache of SeLayer objects. Each SeLayer
object holds a reference to a SeConnection. This is thread unsafe, since we
should create a new SeLayer object every time its needed.
The caching issue was made a time ago more because we was incorrectly accessing
SeLayers, by calling connection.getLayers(), which returns a Vector<SeLayer>
and is too expensive. But creating a new SeLayer(SeConnection, layerName,
spatialCol) is quite inexpensive and much more correct.
--
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: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
