ShapefileRenderer always memory maps the dbf just to grab the dbf header,
causing OOM
-------------------------------------------------------------------------------------
Key: GEOT-1480
URL: http://jira.codehaus.org/browse/GEOT-1480
Project: GeoTools
Issue Type: Bug
Components: ext shapefilerender
Affects Versions: 2.4-RC0
Reporter: Andrea Aime
Assignee: Jesse Eichar
Priority: Critical
Fix For: 2.4-RC1
In a test we're doing we have a 1.1GB dbf file associated to a shapefile. In a
threaded test shapefile renderer fails as soon as 2 client threads are used on
a 2GB machine with an OOM, the first threads succed and maps, leaving not
enough memory to the other.
If the shapefile has not bee instructed to memory map the dbf, it should not
even for just accessing the header.
The test uses a very big dbf, but it's designed to ramp up to 60 client
threads, so the OOM would happen even if the memory mapped file was just 40MB
(a much more common size).
As usual, assigning it to you for review.
--
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.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
