[Geoserver-users] error Java heap space GeoServer 1.7b1

GeoServer GeoServer User
1

Dear all
Recently, when I use Geoserver 1.7, always have this kind of warning information

2008-06-24 19:40:22,046 ERROR [tiles.InsertTag] - ServletException in ‘/WEB-INF/pages/data/styles/Select.jsp’: PermGen space
javax.servlet.ServletException: java.lang.OutOfMemoryError: PermGen space

2008-07-03 16:56:20,722 WARN [geoserver.action] - Unable to fetch a list of FeatureType names from datastore.
java.lang.OutOfMemoryError: Java heap space

Caused by: org.geotools.data.DataSourceException: Connection test failed
at org.geotools.data.jdbc.datasource.DataSourceUtil.buildDefaultDataSource(DataSourceUtil.java:123)
at org.geotools.data.postgis.PostgisDataStoreFactory.getDefaultDataSource(PostgisDataStoreFactory.java:216)
at org.geotools.data.postgis.PostgisDataStoreFactory.createDataStore(PostgisDataStoreFactory.java:193)
at org.vfny.geoserver.util.DataStoreUtils.getDataStore(DataStoreUtils.java:75)
at org.geoserver.catalog.ResourcePool.getDataStore(ResourcePool.java:151)
… 58 more
Caused by: java.lang.IllegalStateException: Timer already cancelled.
at java.util.Timer.sched(Unknown Source)
at java.util.Timer.schedule(Unknown Source)

is there anyone can explain that for me ? such as Out of Memory or Timer already cancelled.
Thanks in advance

All the best

Xiaoyu

–
Xiaoyu Guan (Sam)
Geo-information Science
Wageningen UR

2

Xiaoyu Guan ha scritto:

Dear all
Recently, when I use Geoserver 1.7, always have this kind of warning information

2008-06-24 19:40:22,046 ERROR [tiles.InsertTag] - ServletException in '/WEB-INF/pages/data/styles/Select.jsp': PermGen space
javax.servlet.ServletException: java.lang.OutOfMemoryError: PermGen space

Permgen error are usually an indication that too many classes are being
loaded in the same virtual machine. Do you have various others
web applications besides GeoServer itself?

The way to work around this is to specify a parameter such as
-XX:MaxPermSize=128m
to your virtual machine configuration (as a startup parameter).

It's also a quite common problem occurring when you deploy and
undeploy a number of times java web applications in tomcat,
so if you encouter it after doing a number of redeploys,
just restart the container.

Cheers
Andrea