Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Date: Wed, 25 Jul 2012 18:38:34 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: dev@accumulo.apache.org
Message-ID: <2042083400.102355.1343241514639.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <524980258.98226.1343163994708.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (ACCUMULO-701) No longer seeing
 TApplicationException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner commented on ACCUMULO-701:
---------------------------------------

I looked into this a bit more.  The Processor code generated by 0.6 catches Throwable and returns TApplicationException to the client.  The code generated by 0.8 does not seem to do this.
                
> 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