Hi,
I'm doing some benchmarks on geoserver and I've encountered serious memory
issues on WFS.
I'm requesting lots of GetFeature request (with bbox and filters) on two
instances of geoserver (I used separately versions 2.1.1, 2.1.2 and 2.1.3).
After about 30 minutes, the performance collapses a
On Wed, Aug 10, 2011 at 10:37 AM, Bonnet Axel wrote:
> Last night we made the same bench on the last nightly build available and it
> lasted over 12 hours, so the memory leak has been mainly solved.
>
> But I still got in the logs several ConcurrentModificationException (much
> less than before
Last night we made the same bench on the last nightly build available and it
lasted over 12 hours, so the memory leak has been mainly solved.
But I still got in the logs several ConcurrentModificationException (much less
than before of course), so there may remain some fixings to do.
I can give
On Tue, Aug 9, 2011 at 2:11 PM, Bonnet Axel wrote:
> “GRAVE: The web application [/geoserver] created a ThreadLocal with key of
> type [null] (value [null]) and a value of type
> [org.geotools.data.postgis.WKBAttributeIO] (value
> [org.geotools.data.postgis.WKBAttributeIO@676f0256]) but failed to
Hi,
I'm doing some benchmarks on geoserver and i've encountered serious memory
issues.
I am requesting lots of WFS request (GetFeature with bbox or filters) on two
instances of geoserver 2.1.0.
After about one hour, the performance collapses and the GC logs show memory
problems. On each geose
