On Sun, Apr 15, 2012 at 9:53 PM, Gabriel Roldan <[email protected]> wrote: > apparently we lost the ability of logging the full wms request with > the stack trace. I'll file a bug report about that. > But in any case it looks more like the client is misconfigured or > trying to use the WMS-C end point as a pure WMS. > Check out the list of advertised resolutions for the two gridsets, the > requested one (0.11861801147460932) is way too far from any of them: > <view-source:http://atlas.track.gov.au:8080/geoserver/gwc/demo/HCVAE?gridSet=EPSG:4326&format=image/png> > <view-source:http://atlas.track.gov.au:8080/geoserver/gwc/demo/HCVAE?gridSet=EPSG:900913&format=imag > ise/png> > > I'd say that except if you're actually experiencing this with a valid > request, as your service is public, it looks more like someone is > playing with it with a wms client instead of a wms-c one? > That is, if it turns out it's not a problem in the server, but just a client making bad requests, the log message shouldn't be logged as ERROR, but perhaps just at the debug or info level. Bad user input is not a server problem, and the error response an expected output. Unfortunately both the geoserver and geowebcache code bases are infested of this mistake, presumably just because the developer thought it was easy to catch his attention during testing.
So try to check whether some application if yours or your users is failing when hitting the server with valid input, and if it's not (as it seems to be the case), just ignore the log message. regards, Gabriel ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
