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

Posted to dev@accumulo.apache.org by "John Vines (JIRA)" <ji...@apache.org> on 2012/07/24 23:43:35 UTC

[jira] [Commented] (ACCUMULO-701) No longer seeing TApplicationException

    [ https://issues.apache.org/jira/browse/ACCUMULO-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421793#comment-13421793 ] 

John Vines commented on ACCUMULO-701:
-------------------------------------

Is this a fault of the exception not propagating back or our server side code not spitting the errors back?
                
> No longer seeing TApplicationException
> --------------------------------------
>
>                 Key: ACCUMULO-701
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-701
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> When an unexpected exception occurred server side, the client used to see a TApplicationException on the client side.  It appears this not happening anymore in trunk since the switch to thrift 0.8.  A lot of code depends on the previous behavior.
> Code that used to throw an exception to the client is now getting stuck indefinitely.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira