Remove stacktraces in server logs for handled failures

[GoogleCodeExporter]

Certain operations, when they fail, cause stack traces to be flushed to the 
server logs.
A simple error message in the logs should suffice, and would also better 
express that the failure has been properly handled.

Known examples:

- When posting an update without a body (for parameters). ex:
curl -X POST http://localhost:8020/mybucket/akey/update -H "Content-Type: 
application/json"

- When getting a key that does not exist. ex:
curl -X GET http://localhost:8020/bucket/nokey

- Getting a key with an invalid predicate (or passing in an invalid predicate 
to any operation that takes a predicate). ex:
curl -X GET http://localhost:8020/mybucket/key?predicate=greatballsoffire

- Querying by range with unknown comparator (or passing in an unknown 
comparator to any operation that takes a comparator). ex:
curl -X GET 
"http://localhost:8020/mybucket/range?startKey=start&comparator=bouillabaisse"

I have yet to probe the Map/Reduce & merge-operations for similar failures, but 
I expect to find similar behaviour, especially with MapReduce (since it's heavy 
on named functions, etc).

Original issue reported on code.google.com by johansso...@gmail.com on 23 Jan 2011 at 1:04

[GoogleCodeExporter]

Original comment by johansso...@gmail.com on 23 Jan 2011 at 6:41

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by sergio.b...@gmail.com on 31 Jan 2011 at 5:18

• Added labels: Milestone-0.8.2
• Removed labels: Milestone-0.8.1

[GoogleCodeExporter]

Hey Sven, any estimates for this one? If you're currently too busy, I'll take 
it up if you don't mind.

Original comment by sergio.b...@gmail.com on 12 Mar 2011 at 7:59

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Now, only server error codes (>= 500) get printed with the full stack trace.

Original comment by sergio.b...@gmail.com on 26 Apr 2011 at 10:01

• Changed state: Fixed