New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
respond with 404/500 if map.load() fails #3
Comments
We should already be returning 500 when we encounter an error. When |
try running >= http://trac.mapnik.org/changeset/3258, setting max_size slightly smaller than your libeio threads and then loading the server. Some responses will the plain text errors, which I guessed were not 404's because ab did not report errors (before ab was in "error"?) |
wow - looks like ab does not treat 500's as errors in its report I'm just reading things wrong. anyway, this is working just fine sorry for the false alarm, closing:
|
otherwise failures will look like really fast tile reponses when testing. This is imperitive because we're now seeing layer constructors throw when max_size is reached in the postgres pool
The text was updated successfully, but these errors were encountered: