I am developing and image mosaicing/pyradmid plugin for geotools and did some
tests with geoserver.
The size of the pyramids are beyond some Gigs and the constructor of
CoverageConfig does a test read using 1/20 of the width and hight of the
full extent. That is to much !!!!!!!!!.
I could avoid this situation by shrinking the request envelope but that is
surely not a final solution, so what would be a better solution ?. (Another
way would be to create the config manually)
By the way, if you want to use DB2 JNDI Datasource (using DB2DataStore)
there are 2 preconditions
1) Do not use an XA DataSource
2) Configure your DataSource to HOLD_CURSORS_OVER_COMMIT
thanks in advance
--
View this message in context: http://www.nabble.com/org.vfny.geoserver.config.CoverageConfig-causes-memory-overflow-tp16538111p16538111.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.