You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shindig.apache.org by "Paul Lindner (JIRA)" <ji...@apache.org> on 2009/02/17 20:38:59 UTC

[jira] Resolved: (SHINDIG-914) Better logging of RpcInvocationHandler and RestInvocationHandler exceptions in DefaultHandlerRegistry

     [ https://issues.apache.org/jira/browse/SHINDIG-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Lindner resolved SHINDIG-914.
----------------------------------

    Resolution: Fixed

committed.

Exceptions in handler classes bit me over the weekend, so I think it's important to have this in there...


> 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.