[Geoserver-devel] GeoServer 1.51 kills Tomcat 5.5.17 / JVM process

Hi,

I have been playing a bit with geoserver 1.51. Successfully installed and
connected to ArcSDE 9.1 at the backend. I then played a bit around with
preview of layer as WMS service I can call up the initial view of about
150.000 points and I can grab the slider and zoom in but panning the data
while zoomed in seems to be too much for the software and the entire
Tomcat process dies. I have allocated 512Mb to Tomcat and as soon as I do
anything with Geoserver WMS preview the memory usage explodes when looking
at a Jconsole profile of the VM memory.

The Java hotspot engine have dumped the attached trace files when it dies.
Any clues as to how to resolve this. Am I throwing too much data at it?
(mind you I am zoomed in to a few hundred points on screen when panning
just kills it all.

/Jesper

(attachments)

hs_err_pid2756.log (20 KB)
hs_err_pid5524.log (18.7 KB)

Jesper Kruse Nielsen ha scritto:

Hi,

I have been playing a bit with geoserver 1.51. Successfully installed and
connected to ArcSDE 9.1 at the backend. I then played a bit around with
preview of layer as WMS service I can call up the initial view of about
150.000 points and I can grab the slider and zoom in but panning the data
while zoomed in seems to be too much for the software and the entire
Tomcat process dies. I have allocated 512Mb to Tomcat and as soon as I do
anything with Geoserver WMS preview the memory usage explodes when looking
at a Jconsole profile of the VM memory.

The Java hotspot engine have dumped the attached trace files when it dies.
Any clues as to how to resolve this. Am I throwing too much data at it?
(mind you I am zoomed in to a few hundred points on screen when panning
just kills it all.

Hmmm.... on sigma.geoserver.org we're serving some datasets with millions of points and we aren't experiencing these crashes.
If you can, I would suggest you update your JDK (are you using 1.6.0_02?) and Tomcat version.
Another reason for having this kind of hard crashes is that some
native part has gone wild and teared down the native machine.
Native parts may be JAI, if you installed it fully, the APR
runtime for TomCat and... hum... well, don't know if ArcSDE
datastore has any, I guess not?

Cheers
Andrea