Hi,
I have a server running 1.7.5 and am basically running the packaged version with Jetty. Currently I’m displaying three shape files on a openlayers map, and I’m referencing each shape using the geo web cache plugin. Two of the files work great, but the third one all I see is this warning: “12 Jun 09:38:47 ERROR [geowebcache.GeoWebCacheDispatcher] - Thread 17 Unknown layer metis:parcels_combined. Check the logfiles, it may not have loaded properly.”
This third shape file is huge, as I’ve combined a state’s worth of parcel shape files to form a big one coming in at 665mb (that’s just the .shp file). If I don’t use the caching url by changing “/geoserver/gwc/service/wms?” to “/geoserver/wms?” it works fine, so it has something to do with the caching plugin.
When I go to the demo page for the cache as referenced in documentation the layer isn’t there. I have reloaded and done everything I can think of but the caching stuff just isn’t aware of that layer. Is there a parameter somewhere that tells the cache stuff what criteria is uses to serve a layer? Maybe it’s just a bad idea with this big of a shape file to do this?
Thanks in advance.
Thanks,
Clark
Clark Endrizzi wrote:
Hi,
I have a server running 1.7.5 and am basically running the packaged version with Jetty. Currently I'm displaying three shape files on a openlayers map, and I'm referencing each shape using the geo web cache plugin. Two of the files work great, but the third one all I see is this warning: "12 Jun 09:38:47 ERROR [geowebcache.GeoWebCacheDispatcher] - Thread 17 Unknown layer metis:parcels_combined. Check the logfiles, it may not have loaded properly."
This third shape file is huge, as I've combined a state's worth of parcel shape files to form a big one coming in at 665mb (that's just the .shp file). If I don't use the caching url by changing "/geoserver/gwc/service/wms?" to "/geoserver/wms?" it works fine, so it has something to do with the caching plugin.
When I go to the demo page for the cache as referenced in documentation the layer isn't there. I have reloaded and done everything I can think of but the caching stuff just isn't aware of that layer. Is there a parameter somewhere that tells the cache stuff what criteria is uses to serve a layer? Maybe it's just a bad idea with this big of a shape file to do this?
Thanks in advance.
Thanks,
Clark
As the message says, the layer probably just failed to load. I'm not aware of any problems like this, so you'll have to dig a little:
1) Stop jetty , make the command line window where you run Jetty quite big, then start it again.
2) Point your browser to http://localhost:8080/geoserver/gwc/demo , this should trigger loading all the layers.
3) Check the command line window to see if you find a traceback or other error messages.
Alternatively, if your instance is publicly accessible you can send me the URL off list.
-Arne
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
Hi Arne,
Did you get my email I sent you? Just wanted to confirm.
Thanks,
Clark Endrizzi
On Fri, Jun 12, 2009 at 10:08 AM, Clark Endrizzi <cendrizzi@anonymised.com> wrote:
Hi,
I have a server running 1.7.5 and am basically running the packaged version with Jetty. Currently I’m displaying three shape files on a openlayers map, and I’m referencing each shape using the geo web cache plugin. Two of the files work great, but the third one all I see is this warning: “12 Jun 09:38:47 ERROR [geowebcache.GeoWebCacheDispatcher] - Thread 17 Unknown layer metis:parcels_combined. Check the logfiles, it may not have loaded properly.”
This third shape file is huge, as I’ve combined a state’s worth of parcel shape files to form a big one coming in at 665mb (that’s just the .shp file). If I don’t use the caching url by changing “/geoserver/gwc/service/wms?” to “/geoserver/wms?” it works fine, so it has something to do with the caching plugin.
When I go to the demo page for the cache as referenced in documentation the layer isn’t there. I have reloaded and done everything I can think of but the caching stuff just isn’t aware of that layer. Is there a parameter somewhere that tells the cache stuff what criteria is uses to serve a layer? Maybe it’s just a bad idea with this big of a shape file to do this?
Thanks in advance.
Thanks,
Clark