After bombarding the GeoServer with requests for hours, it uses up all given
memory and throws an Out Of Memory exception.
Increasing the size with -Xmx makes it run longer but ends the same. The
strategy is set to SPEED. I've tried the setting Maximum features to less
but this doesn't seem to make any visual difference in the images returned.
Maybe I have misunderstood this parameter. After stoping the requests
pouring in Geoserver memory usage soon falls down again.
Is there a way to make it run indefinitelly no matter how much is requested
of it?
I'm using the 1.3.4a stable release for win32 and run it with:
"C:\Program Files\Java\j2sdk1.4.2_12\bin\java.exe"
-DGEOSERVER_DATA_DIR="..\data_dir" -Xms1000m -Xmx1000m -jar start.jar
--
View this message in context: http://www.nabble.com/Geoserver-Out-Of-Memory-tf2387249.html#a6655049
Sent from the GeoServer - User mailing list archive at Nabble.com.
pudding ha scritto:
After bombarding the GeoServer with requests for hours, it uses up all given
memory and throws an Out Of Memory exception.
Increasing the size with -Xmx makes it run longer but ends the same. The
strategy is set to SPEED. I've tried the setting Maximum features to less
but this doesn't seem to make any visual difference in the images returned.
Maybe I have misunderstood this parameter. After stoping the requests
pouring in Geoserver memory usage soon falls down again.
Is there a way to make it run indefinitelly no matter how much is requested
of it?
I'm using the 1.3.4a stable release for win32 and run it with:
"C:\Program Files\Java\j2sdk1.4.2_12\bin\java.exe"
-DGEOSERVER_DATA_DIR="..\data_dir" -Xms1000m -Xmx1000m -jar start.jar
Interesting. Can you describe your setting?
Which data stores are you using?
Which kind of requests are you performing?
If you have written an automate test with java and you can also share the data set, it would
be nice to have both 
Cheers
Andrea Aime
pudding ha scritto:
After bombarding the GeoServer with requests for hours, it uses up all given
memory and throws an Out Of Memory exception.
Increasing the size with -Xmx makes it run longer but ends the same. The
strategy is set to SPEED. I've tried the setting Maximum features to less
but this doesn't seem to make any visual difference in the images returned.
Maybe I have misunderstood this parameter. After stoping the requests
pouring in Geoserver memory usage soon falls down again.
Is there a way to make it run indefinitelly no matter how much is requested
of it?
I'm using the 1.3.4a stable release for win32 and run it with:
"C:\Program Files\Java\j2sdk1.4.2_12\bin\java.exe"
-DGEOSERVER_DATA_DIR="..\data_dir" -Xms1000m -Xmx1000m -jar start.jar
Ok, I've opened a Jira issue for this:
http://jira.codehaus.org/browse/GEOS-729
I still need as much information as you can give me in order to reproduce the bug thought.
Cheers
Andrea Aime
i have encountered the same problem. i write an automation code to get data
from the Geoserver(deploy in my local computer). and after 6 - 7 hours
running. the error come out. print:
java.lang.OutOfMemoryError: java heap space
Exception in thread "btpool0-7" java.lang.OutOfMemoryError:java heap space.
my computer sys info:
1G memory + Core2 CPU 1.83G
when the application running. i found 1.09 G memory used total. and the
postgresql used 100% one cpu.
--
View this message in context: http://www.nabble.com/Geoserver-Out-Of-Memory-tp6655049p20914958.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
anigold ha scritto:
i have encountered the same problem. i write an automation code to get data
from the Geoserver(deploy in my local computer). and after 6 - 7 hours
running. the error come out. print:
java.lang.OutOfMemoryError: java heap space
Exception in thread "btpool0-7" java.lang.OutOfMemoryError:java heap space.
my computer sys info:
1G memory + Core2 CPU 1.83G
when the application running. i found 1.09 G memory used total. and the
postgresql used 100% one cpu.
There is a number of ways that could have happened.
Can you report the OutOfMemoryError stack traces that you should
have in $GEOSERVER_DATA_DIR/logs/geoserver.log?
(you have them if you're running with at least JDK 1.6.0)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
anigold ha scritto:
hi. Andrea
the attachment is the log file your asked.pls check it.
and forgot to say, the version is Geoserver 1.6.5. and i install it in windows XP + SP2.
Ah, 1.6.5. There was a memory leak related to WFS request parsing
that has been fixed in GeoServer 1.7.0, and I see you had quite
a bit of WFS requests before the OOM.
Actually 1.7.1 is out, so I'd suggest you try out that one.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
anigold ha scritto:
hi. Andrea
the attachment is the log file your asked.pls check it.
and forgot to say, the version is Geoserver 1.6.5. and i install it in windows XP + SP2.
Ah, 1.6.5. There was a memory leak related to WFS request parsing
that has been fixed in GeoServer 1.7.0, and I see you had quite
a bit of WFS requests before the OOM.
Interesting to know. Could you please point me to the JIRA issue related to this problem and maybe give me some directions on how to fix it on 1.6.5? I would like to fix some installed geoservers using 1.6.5 without updating them to 1.7.0. If I can produce a patch I would be glad to share it with other people interested in it.
Mauro
Not easy. I tried to backport as much of the patch from 1.7.0 to 1.6.x as best i could. I got another
user to try it out and they still had problems so its probably another issue.
I know this is probably a long shot but what would be extremely helpful would
be that is having these issues to run GeoServer in a profiler and share the result.
-Justin
Mauro Bartolomeoli wrote:
Andrea Aime wrote:
anigold ha scritto:
hi. Andrea
the attachment is the log file your asked.pls check it.
and forgot to say, the version is Geoserver 1.6.5. and i install it in windows XP + SP2.
Ah, 1.6.5. There was a memory leak related to WFS request parsing
that has been fixed in GeoServer 1.7.0, and I see you had quite
a bit of WFS requests before the OOM.
Interesting to know. Could you please point me to the JIRA issue related to this problem and maybe give me some directions on how to fix it on 1.6.5? I would like to fix some installed geoservers using 1.6.5 without updating them to 1.7.0. If I can produce a patch I would be glad to share it with other people interested in it.
Mauro
------------------------------------------------------------------------
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Mauro Bartolomeoli ha scritto:
Andrea Aime wrote:
anigold ha scritto:
hi. Andrea
the attachment is the log file your asked.pls check it.
and forgot to say, the version is Geoserver 1.6.5. and i install it in windows XP + SP2.
Ah, 1.6.5. There was a memory leak related to WFS request parsing
that has been fixed in GeoServer 1.7.0, and I see you had quite
a bit of WFS requests before the OOM.
Interesting to know. Could you please point me to the JIRA issue related to this problem and maybe give me some directions on how to fix it on 1.6.5? I would like to fix some installed geoservers using 1.6.5 without updating them to 1.7.0. If I can produce a patch I would be glad to share it with other people interested in it.
For the record the jira is here:
http://jira.codehaus.org/browse/GEOS-2265
http://jira.codehaus.org/browse/GEOT-2064
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Justin Deoliveira wrote:
Not easy. I tried to backport as much of the patch from 1.7.0 to 1.6.x as best i could. I got another
user to try it out and they still had problems so its probably another issue.
I know this is probably a long shot but what would be extremely helpful would
be that is having these issues to run GeoServer in a profiler and share the result.
I downloaded the last version of the xml-xsd package for 2.4.x from hudson (that version seems to have your patch applied); from the first tests it seems quite better in memory usage.
Thanks,
Mauro