Hey there, sorry for the slow turn around (tired of saying that, but
So it looks like there's potentially more than one thing going on
here, I can't tell for sure from your problem description.
Unfortunately I don't have the time right now to check for each one,
but lets go step by step.
First off, it'd be cool if you can send me your geowebcache.xml and
explain how you're configuring your layer, whether it's a separate
wmsLayer in geowebcache.xml or just the embedded geoserver one.
Second, I would highly recommend you to try the latest trunk nightly,
if not for anything else just to find out whether/which of the
problems you mention are already fixed. Hopefully they all are, except
perhaps the port number one,if that turns out to be a bug. But what
you can do in trunk is to configure your embedded layer through the
GeoServer UI and assign it any gridset, instead of the limited 4326
and 900913 ones that comes by default with any previous version.
Sorry I can't dig in deeper now, but if you send your config file I
can try it out with more ease.
On Tue, Mar 6, 2012 at 3:25 PM, cheesybiscuits
> Hi Gabriel thanks for your input. I think I might have discovered an issue
> with specifying the port number on geowebcache.xml's wmsUrl element -
> explained further below.
> I am using GeoServer 2.1.3, sorry for not mentioning in my original message
> - I knew I would leave something out!
> Also I think it's worth explaining exactly what I'm hoping to achieve in
> case this points to any obvious issues. I have a version of Oracle that
> doesn't support 900913 (aka 3875) so I am having to work around this. I
> transformed my original data (in 4326) to 3785 (this is not a typo) with a
> 'USE_SPHERICAL' argument as described here:
> https://forums.oracle.com/forums/thread.jspa?threadID=2228982. The end
> result is coordinates that align almost perfectly (sub-millimetre) with the
> same locations in 900913.
> With the bulid of OpenLayers I am using (2.11 Release) it does not seem
> possible to request two layers for the same map with different projections -
> though I'm told the trunk might offer this capability - so I can't ask
> GeoServer to give me my adjusted 3785 'live' data and GWC to give me the
> 900913 cached data, even though they should line up just fine. So... what
> I'm trying to do here is define a 3785 gridset in GWC which is actually
> using 900913 behind the scenes, so that OpenLayers can request both live and
> cached layers in 3785.
> The gridset in geowebcache.xml looks like this:
> Trying to preview the layer via GWC gives this in the GeoServer log: ERROR
> [geowebcache.GeoWebCacheDispatcher] - All backends (1) failed. Reason:
> Unexpected response code from backend: 404 for
> http://host_name:8080/geoserver/test/wms?. Last request:
> When I look at the Apache access log I see the 404 requests like this:
> If I copy and paste that same URL into a browser, but prefixed with
> http://host_name:8080 I get a 200 response and an image. This was mighty
> confusing, but then I realised I would get a 404 if the request actually
> went to http://host_name:80/... I updated and reloaded geowebcache.xml with
> a random port number and I get the same result. Is it possible that GWC is
> ignoring the port number in the wmsUrl element?
> Also, I'd really like to see how the default gridsets and layers added by
> GeoServer are configured - is there an xml config file buried somewhere for
> layers which work that I can use as a reference?
> Any feedback much appreciated.
> View this message in context: http://osgeo-org.1560.n6.nabble.com/GeoWebCache-geowebcache-xml-bug-custom-GridSet-and-applying-it-to-a-layer-tp4538078p4552096.html
> Sent from the GeoServer - User mailing list archive at Nabble.com.
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> Geoserver-users mailing list
OpenGeo - http://opengeo.org
Expert service straight from the developers.