Commit 052adbed authored by Guido van Rossum's avatar Guido van Rossum

When a call in the server raises an exception that is passed back to

the client, don't log it at the ERROR level.  If it really was a
disaster, the client should log it.  But if the client was expecting
the exception, the esrver shouldn't get all upset about it.  Change
this to the INFO level.  (When it *is* considered an error by the
client, it's useful to be able to see the server-side traceback in the
log.)
parent b1cffb9f
...@@ -232,7 +232,7 @@ class Connection(smac.SizedMessageAsyncConnection): ...@@ -232,7 +232,7 @@ class Connection(smac.SizedMessageAsyncConnection):
# there are several cases where this happens during the # there are several cases where this happens during the
# normal course of action, shouldn't this be logged at the # normal course of action, shouldn't this be logged at the
# INFO level? # INFO level?
log("%s() raised exception: %s" % (name, msg), zLOG.ERROR, log("%s() raised exception: %s" % (name, msg), zLOG.INFO,
error=error) error=error)
error = error[:2] error = error[:2]
return self.return_error(msgid, flags, *error) return self.return_error(msgid, flags, *error)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment