You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2012/07/24 23:06:34 UTC
[jira] [Created] (ACCUMULO-701) No longer seeing
TApplicationException
Keith Turner created ACCUMULO-701:
-------------------------------------
Summary: 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
[jira] [Commented] (ACCUMULO-701) No longer seeing
TApplicationException
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Assigned] (ACCUMULO-701) No longer seeing
TApplicationException
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Turner reassigned ACCUMULO-701:
-------------------------------------
Assignee: Keith Turner
> No longer seeing TApplicationException
> --------------------------------------
>
> Key: ACCUMULO-701
> URL: https://issues.apache.org/jira/browse/ACCUMULO-701
> Project: Accumulo
> Issue Type: Bug
> Reporter: Keith Turner
> Assignee: 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
[jira] [Commented] (ACCUMULO-701) No longer seeing
TApplicationException
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422510#comment-13422510 ]
Keith Turner commented on ACCUMULO-701:
---------------------------------------
Opened THRIFT-1658
> 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
[jira] [Commented] (ACCUMULO-701) No longer seeing
TApplicationException
Posted by "John Vines (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (ACCUMULO-701) No longer seeing
TApplicationException
Posted by "Keith Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421797#comment-13421797 ]
Keith Turner commented on ACCUMULO-701:
---------------------------------------
When I turn debug on in the shell, I am seeing TTransportException. Because I am seeing this exception, I suspect the server is just closing the connection but I am not sure.
> 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