Thanks Andrea, my workaround was to pass as parameter to the jvm -XX:MaxPermSize=128M.
If I understand it correctly, that parameter limits the size of memory the garbage collector can take: so although with memory leaks, it won't invade the other portions of memory assigned to the jvm and the application will work. best, amaneiro On 20/04/11 16:05, Andrea Aime wrote: > 2011/4/20 Andrés Maneiro<[email protected]>: > GeoServer uses a large amount of libraries, as a result it has a large > footprint > in the permgenspace. > > I normally give between 128MB and 256MB of perm gen space to GeoServer, > and avoid redeploying it without also restarting the container (which is also > what the blog suggests). > ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
