[GeoNetwork-users] serious performance problems with GeoNetwork and Tomcat6

Hello,

We are running GeoNetwork in tomcat6 on a Debian Squeeze server (see specs below).

We currently have 5 students working in parallel to encode metadata of our maps. Very regularly the system completely freezes up and the students cannot work anymore (their browser just runs indefinitely trying to connect to geonetwork).

As you can see from the specs, we have increased max heap size of tomcat to the enormous value of 9GB. Following the tomcat process in visualvm, we can see that it goes up to 7-8 GB of used heap.

We had a series of "java.lang.OutOfMemoryError: GC overhead limit exceeded" errors. Using -XX:-UseGCOverheadLimit, those do not appear anymore, but we still see the freezes.

I now see the following message in the logs:

"GRAVE: The web application [/geoserver] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation."

Can anyone give me a hint as to the direction I should look into ? 8GB of memory usage just does not seem right to me...

***************************
Specs of the server:

8 x Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz
12GB RAM

Tomcat version: 6.0.35-1+squeeze2

with

JAVA_OPTS="-Djava.awt.headless=true -Xmx9g -XX:MaxPermSize=256m -XX:+UseParallelGC -XX:NewRatio=3 -XX:-UseGCOverheadLimit"

Geonetwork version: 2.6.4-0

GeoServer 2.1.3 is also running.
*****************************

Moritz

On 04/07/12 12:19, Moritz Lennert wrote:

Hello,

We are running GeoNetwork in tomcat6 on a Debian Squeeze server (see
specs below).

We currently have 5 students working in parallel to encode metadata of
our maps. Very regularly the system completely freezes up and the
students cannot work anymore (their browser just runs indefinitely
trying to connect to geonetwork).

[...]

***************************
Specs of the server:

[...]

GeoServer 2.1.3 is also running.
*****************************

I should have tried this earlier, but taking geoserver out of the /var/lib/tomcat6/webapps directory and restarting tomcat brings memory usage down to reasonable levels (<512MB).

So the problem seems to be with GeoServer, not GeoNetwork.

Sorry for the noise.

Moritz