[
https://issues.apache.org/jira/browse/AVRO-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453470#comment-13453470
]
Brock Noland commented on AVRO-1156:
------------------------------------
I am +1 for throwing Error. Outside of some cases where you are actually
allocating large amounts of memory or loading native libraries, catching
Error(s) is dangerous. I have seen a large number of scenarios where this
causes problems which are very hard to debug, as Mike mentions.
> Avro responder swallows thrown Errors
> -------------------------------------
>
> Key: AVRO-1156
> URL: https://issues.apache.org/jira/browse/AVRO-1156
> Project: Avro
> Issue Type: Bug
> Reporter: Mike Percy
> Assignee: Mike Percy
> Fix For: 1.7.2
>
> Attachments: AVRO-1156-1.patch
>
>
> The Avro responder wraps caught Errors, such as OutOfMemoryErrors, in
> Exceptions and rethrows them. That's problematic because an Error should be
> allowed to crash the JVM, since it's often irrecoverable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
