Hi list,
I am writing this email to expose an annoying problem Me and Alessio
are having with rendering.
The WCS we are developing for GeoServer basically gives the WMS the
possibility to render rasters and features.
When we render only raster, everything is fine, the memory usage is
high but at the end of the rendering we are able to reclaim it.
When we render only features the WMS uses less memory and it frees it
without problems.
The problem is when we try to render both features and
GridCoverages2D. We achieve this by simply asking to a
DefaultMapContext object from GeoTools to add a layer formed by a
GridCoverage2D. Well in such situations we experience an uncontrolled
growth of the heap size. We have started to inspect the heap with
JProbe but so far with no real luck. Our guess is that maybe something
strange happens when rendering both types of data but so far we have
not been able to spot the problem exactly.
I hope someone had some ideas on this.
SImone.