Geoserver-users - Re ndering request error

I tried to view my layer using KML and recieved the error below. Does anyone
know what would cause this error? My layer only has about 50 features in it.
thanks
Dan

14 Jul 15:30:14 ERROR [geoserver.ows] -
org.vfny.geoserver.wms.WmsException: Rendering request would use 69632KB,
whilst the maximum memory
allowed is 65536KB
at
org.vfny.geoserver.wms.responses.DefaultRasterMapProducer.produceMap(DefaultRasterMapProd
ucer.java:241)
at
org.vfny.geoserver.wms.responses.map.kml.KMZMapProducer.writeTo(KMZMapProducer.java:162)
at
org.vfny.geoserver.wms.responses.GetMapResponse.writeTo(GetMapResponse.java:637)
at
org.geoserver.ows.adapters.ResponseAdapter.write(ResponseAdapter.java:60)
at org.geoserver.ows.Dispatcher.response(Dispatcher.java:726)
at
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:234)
at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.j
ava:153)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControlle
rHandlerAdapter.java:48)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571
)
at
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
at
org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter
.java:108)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java
:265)
at
org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityIntercepto
r.java:107)
at
org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityIntercep
tor.java:72)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java
:275)
at
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:
124)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java
:275)
at
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcess
ingFilter.java:125)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java
:275)
at
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:
174)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java
:275)
at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContext
IntegrationFilter.java:249)
at
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java
:275)

Dan MacLeod ha scritto:
For some reason the KMZ map producer is trying to build a raster overlay
that would require 65MB of memory to be generated, which is an insane
size, roughly 8300x8300. The maximum render size protection triggers
and disallows such a big raster to be created
Now sure why such a big raster is required, but you can try to increase
the maximum memory allowed for a single request.
If you can share the dataset and the sld please attach them to a
bug report at jira.codehaus.org, so that we can have a look at it
when time allows.
Cheers
Andrea

The error appears to be with my SLD. I currently have 16 FeatureTypeStyle
elements. If I add one more the problem appears. If I remove it again, then
everything works. So it seems like there is a limit to the number of
FeatureTypeStyle elements allowed in a SLD. Is this the case? If so, is
there a way to use multiple SLD's for a layer? My SLD is listed below.
thanks
Dan

Entities

Entities
C2 Entities





TYPE
NFAC






image/png


1.0


26









TYPE
NAS






image/png


1.0


26










TYPE
MISSION


SEVERITY
1


GEOMETRY-TYPE-ID
POLYGON





#00FF00
0.5


#000000
1









TYPE
MISSION


SEVERITY
1


GEOMETRY-TYPE-ID
POINT







image/png


1.0


26










TYPE
MISSION


SEVERITY
1


GEOMETRY-TYPE-ID
PATH





#00FF00
2
1.0









TYPE
MISSION


SEVERITY
2


GEOMETRY-TYPE-ID
POLYGON





#0000FF
0.5


#000000
1









TYPE
MISSION


SEVERITY
2


GEOMETRY-TYPE-ID
POINT







image/png


1.0


26










TYPE
MISSION


SEVERITY
2


GEOMETRY-TYPE-ID
PATH





#0000FF
2
1.0









TYPE
MISSION


SEVERITY
3


GEOMETRY-TYPE-ID
POLYGON





#FF9900
0.5


#000000
1









TYPE
MISSION


SEVERITY
3


GEOMETRY-TYPE-ID
POINT







image/png


1.0


26










TYPE
MISSION


SEVERITY
3


GEOMETRY-TYPE-ID
PATH





#FF9900
2
1.0









TYPE
MISSION


SEVERITY
4


GEOMETRY-TYPE-ID
POLYGON





#FFFF00
0.5


#000000
1









TYPE
MISSION


SEVERITY
4


GEOMETRY-TYPE-ID
POINT







image/png


1.0


26










TYPE
MISSION


SEVERITY
4


GEOMETRY-TYPE-ID
PATH





#FFFF00
2
1.0









TYPE
MISSION


SEVERITY
5


GEOMETRY-TYPE-ID
POLYGON





#FF0000
0.5


#000000
1









TYPE
MISSION


SEVERITY
5


GEOMETRY-TYPE-ID
POINT







image/png


1.0


26










TYPE
MISSION


SEVERITY
5


GEOMETRY-TYPE-ID
PATH





#FF0000
2
1.0

Rendering a layer using a 16-featuretypestyle SLD takes about 16 times
as much memory as using a style with one featuretypestyle. Where you
don't actually care about the stacking order, you should keep things in
a single featuretypestyle.
It looks like no two rules from your style will affect the same feature,
so it should be safe for you to consolidate into one featuretypestyle;
this should help things a lot.