[
https://issues.apache.org/jira/browse/SHINDIG-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673317#action_12673317
]
Chico Charlesworth commented on SHINDIG-914:
--------------------------------------------
As long as I can see the stacktrace to where the exception occured, I'm not too
fussed where the exceptions are logged :)
But I see your point Adam .. so where would be the preferred location to log
these exceptions? In ApiServlet.responseItemFromException()?
And I'm good w/ lowering the log level to WARNING if that's deemed more
appropriate ..
> Better logging of RpcInvocationHandler and RestInvocationHandler exceptions
> in DefaultHandlerRegistry
> -----------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-914
> URL: https://issues.apache.org/jira/browse/SHINDIG-914
> Project: Shindig
> Issue Type: Improvement
> Components: Java
> Affects Versions: trunk
> Reporter: Chico Charlesworth
> Fix For: trunk
>
> Attachments: fix-914-744074-improvement.patch
>
>
> When an exception occurs in RpcInvocationHandler or RestInvocationHandler
> execute methods, they get wrapped in a ImmediateFuture.errorInstance(), but
> the original exception stacktrace isn't logged anywhere, so would be better
> to log this exception before returning the ImmediateFuture.errorInstance().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
