Interesting, looking at the code in GeoServerSecurityManager I found the
following snippet
/*
* list of file watchers
* TODO: we should probably manage these better rather than just
throwing them in a
* list, repeated loads will cause this list to fill up with threads
On Sat, Feb 23, 2013 at 4:48 PM, Christian Mueller <
christian.muel...@os-solutions.at> wrote:
> Interesting, looking at the code in GeoServerSecurityManager I found the
> following snippet
>
> /*
> * list of file watchers
> * TODO: we should probably manage these better rather
On Sat, Feb 23, 2013 at 12:31 PM, Andrea Aime
wrote:
> I'm not sure what might cause this, but a reasonable candidate could be
> configuration
> reloads, are you issuing those commands frequently?
>
Hum... I've tried to reload/clear the configuration, and edit users and
roles, but
the threads wat
On Fri, Feb 22, 2013 at 6:02 PM, Eric Smets wrote:
> After a while the geoserver stops functionning due to memory exhaustion,
> this
> comes from the
> fact that more than 10.000 threads are in the following type of status.
> Which
> causes the geoserver
> and other tomcat applications to hang.
Hello,
We have a geoserver 2.2 running in production environment on linux running
openjdk 1.6.
After a while the geoserver stops functionning due to memory exhaustion, this
comes from the
fact that more than 10.000 threads are in the following type of status. Which
causes the geoserver
and oth
