erlang: Don't print a warning for application-defined exceptions
authorDavid Reiss <dreiss@apache.org>
Mon, 30 Aug 2010 22:05:12 +0000 (22:05 +0000)
committerDavid Reiss <dreiss@apache.org>
Mon, 30 Aug 2010 22:05:12 +0000 (22:05 +0000)
Application-defined exceptions are a normal occurrence as far as the
Thrift infrastructure is concerned, so we should not print a warning.

git-svn-id: https://svn.apache.org/repos/asf/incubator/thrift/trunk@990967 13f79535-47bb-0310-9956-ffa450edef68

lib/erl/src/thrift_processor.erl

index e26fb33..913e59b 100644 (file)
@@ -87,7 +87,7 @@ handle_function_catch(State = #thrift_processor{service = Service},
             ok;
 
         {throw, Exception} when is_tuple(Exception), size(Exception) > 0 ->
-            error_logger:warning_msg("~p threw exception: ~p~n", [Function, Exception]),
+            %error_logger:warning_msg("~p threw exception: ~p~n", [Function, Exception]),
             handle_exception(State, Function, Exception),
             ok;   % we still want to accept more requests from this client