Hi,
I am having issues when trying to upgrade our Geoserver from version 1.5.1 to 1.6.3. I am trying to deploy on Red Hat Linux with Tomcat. The first time I deployed the Geoserver war file, it crashed Tomcat and there was an OutOfMemory error in the Tomcat logs. I boosted Tomcat memory by adding the line
JAVA_OPTS=-Xmx1024M
in catalina.sh. The next time, I was able to deploy the Geoserver war file and visit the entry page. So then I tried to perform the upgrade by copying over the data directory with the data directory from our older Geoserver. I was able to go to the entry page for the new Geoserver and things looked good (although the green status bars were partly red). However, immediately when I tried to login, Tomcat once again crashed.
My first question is - are there any known issues with Geoserver 1.6.3 taking up a lot of memory? If there are, am I properly increasing memory to Tomcat? Lastly, am I performing the upgrade properly by simply copying over the data directory?
I had these same issues when I tried to upgrade to version 1.6.2a.
Thanks,
Scott
Scott Pezanowski
email: scottpez@anonymised.com
Scott,
I recently upgraded from 1.4 to 1.6.2, on Red Hat and Tomcat, and after a few (many!?!?) tweaks, things are running well with these JAVA_OPTS=
-Xms128 -Xmx512m
-XX:MaxPermSIze=256m
And another line that really seems to help, which Andrea suggested:
export MALLOC_CHECK=0
that helps prevent glibc errors.
-Steve
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
From: geoserver-users-bounces@lists.sourceforge.net [mailto:geoserver-users-bounces@lists.sourceforge.net] On Behalf Of Scott Pezanowski
Sent: Wednesday, April 09, 2008 1:14 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] problems when ugrading geoserver to version 1.6.3
Hi,
I am having issues when trying to upgrade our Geoserver from version 1.5.1 to 1.6.3. I am trying to deploy on Red Hat Linux with Tomcat. The first time I deployed the Geoserver war file, it crashed Tomcat and there was an OutOfMemory error in the Tomcat logs. I boosted Tomcat memory by adding the line
JAVA_OPTS=-Xmx1024M
in catalina.sh. The next time, I was able to deploy the Geoserver war file and visit the entry page. So then I tried to perform the upgrade by copying over the data directory with the data directory from our older Geoserver. I was able to go to the entry page for the new Geoserver and things looked good (although the green status bars were partly red). However, immediately when I tried to login, Tomcat once again crashed.
My first question is - are there any known issues with Geoserver 1.6.3 taking up a lot of memory? If there are, am I properly increasing memory to Tomcat? Lastly, am I performing the upgrade properly by simply copying over the data directory?
I had these same issues when I tried to upgrade to version 1.6.2a.
Thanks,
Scott
Scott Pezanowski
email: scottpez@anonymised.com
Steve,
Thanks for the tips. I added the options you suggested for JAVA_OPTS as well as the MALLOC_CHECK variable. Things seem to be running very smoothly now and I was able to complete the upgrade.
Thanks,
Scott
Scott Pezanowski
email: scottpez@anonymised.com
From: src176@anonymised.com
To: scottpez@anonymised.com95…; geoserver-users@lists.sourceforge.net
Subject: RE: [Geoserver-users] problems when ugrading geoserver to version 1.6.3
Date: Wed, 9 Apr 2008 15:16:41 -0400
Scott,
I recently upgraded from 1.4 to 1.6.2, on Red Hat and Tomcat, and after a few (many!?!?) tweaks, things are running well with these JAVA_OPTS=
-Xms128 -Xmx512m
-XX:MaxPermSIze=256m
And another line that really seems to help, which Andrea suggested:
export MALLOC_CHECK=0
that helps prevent glibc errors.
-Steve
Stephen Crawford
Center for Environmental Informatics
The Pennsylvania State University
From: geoserver-users-bounces@lists.sourceforge.net [mailto:geoserver-users-bounces@lists.sourceforge.net] On Behalf Of Scott Pezanowski
Sent: Wednesday, April 09, 2008 1:14 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] problems when ugrading geoserver to version 1.6.3
Hi,
I am having issues when trying to upgrade our Geoserver from version 1.5.1 to 1.6.3. I am trying to deploy on Red Hat Linux with Tomcat. The first time I deployed the Geoserver war file, it crashed Tomcat and there was an OutOfMemory error in the Tomcat logs. I boosted Tomcat memory by adding the line
JAVA_OPTS=-Xmx1024M
in catalina.sh. The next time, I was able to deploy the Geoserver war file and visit the entry page. So then I tried to perform the upgrade by copying over the data directory with the data directory from our older Geoserver. I was able to go to the entry page for the new Geoserver and things looked good (although the green status bars were partly red). However, immediately when I tried to login, Tomcat once again crashed.
My first question is - are there any known issues with Geoserver 1.6.3 taking up a lot of memory? If there are, am I properly increasing memory to Tomcat? Lastly, am I performing the upgrade properly by simply copying over the data directory?
I had these same issues when I tried to upgrade to version 1.6.2a.
Thanks,
Scott
Scott Pezanowski
email: scottpez@anonymised.com
Stephen Crawford ha scritto:
Scott,
I recently upgraded from 1.4 to 1.6.2, on Red Hat and Tomcat, and after a few (many!?!?) tweaks, things are running well with these JAVA_OPTS=
-Xms128 -Xmx512m
-XX:MaxPermSIze=256m
Hum, curious, I'm running GeoServer for testing purposes without any of those settings, which means I do run it with 64MB of memory without issues.
Maybe there are other applications running in the same tomcat? That
would explain why you get OOM, since GeoServer is using lots and lots
of classes and saturates pretty quickly the permgen (but not by itself,
there should be some other application helping it 
)
Cheers
Andrea
To tell you the truth, I was having real problems when I first changed from
1.4 to 1.6.0, then 1.6.1. I was trying so many different things to keep
Tomcat running for more than a day. The upgrade to 1.6.2 and my addition of
MALLOC_CHECK=0 both happened around the same time, and I'm not really sure
which change actually fixed everything. So I haven't tried backing things
off to 64MB, since it's all working so well....I'm afraid to touch it!
The only other apps in Tomcat are little servlets I wrote to make certain
postGIS queries that I couldn't do with Geoserver. I'm not enough of a Java
programmer to know if these servlets are doing any harm, but like I said, it
all seems to work now....I haven't had to restart Tomcat in the month since
my final upgrade.
-Steve
-----Original Message-----
From: geoserver-users-bounces@lists.sourceforge.net
[mailto:geoserver-users-bounces@lists.sourceforge.net] On Behalf Of Andrea
Aime
Sent: Wednesday, April 09, 2008 3:59 PM
To: Stephen Crawford
Cc: geoserver-users@lists.sourceforge.net; 'Scott Pezanowski'
Subject: Re: [Geoserver-users] problems when ugrading geoserver to version
1.6.3
Stephen Crawford ha scritto:
Scott,
I recently upgraded from 1.4 to 1.6.2, on Red Hat and Tomcat, and
after a few (many!?!?) tweaks, things are running well with these
JAVA_OPTS=
-Xms128 -Xmx512m
-XX:MaxPermSIze=256m
Hum, curious, I'm running GeoServer for testing purposes without any of
those settings, which means I do run it with 64MB of memory without issues.
Maybe there are other applications running in the same tomcat? That would
explain why you get OOM, since GeoServer is using lots and lots of classes
and saturates pretty quickly the permgen (but not by itself, there should be
some other application helping it )
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss
this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao
ne
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users