[
https://issues.apache.org/jira/browse/AVRO-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453473#comment-13453473
]
Mike Percy commented on AVRO-1156:
----------------------------------
To add a bit more information here, I'm seeing stack traces along the lines of
the following:
WARN ipc.Responder: user error
java.lang.Exception: java.lang.OutOfMemoryError: Java heap space
at
org.apache.avro.ipc.specific.SpecificResponder.respond(SpecificResponder.java:93)
at org.apache.avro.ipc.Responder.respond(Responder.java:149)
at
org.apache.avro.ipc.NettyServer$NettyServerAvroHandler.messageReceived(NettyServer.java:158)
at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
at
org.apache.avro.ipc.NettyServer$NettyServerAvroHandler.handleUpstream(NettyServer.java:143)
at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:783)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:321)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:214)
at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
... snip ...
Caused by: java.lang.OutOfMemoryError: Java heap space
and
WARN ipc.Responder: system error
org.apache.avro.AvroRuntimeException: Unknown datum type: java.lang.Exception:
java.lang.OutOfMemoryError: Java heap space
at org.apache.avro.generic.GenericData.getSchemaName(GenericData.java:574)
at org.apache.avro.generic.GenericData.resolveUnion(GenericData.java:539)
at
org.apache.avro.generic.GenericDatumWriter.resolveUnion(GenericDatumWriter.java:137)
at org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:70)
at org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:57)
at
org.apache.avro.ipc.specific.SpecificResponder.writeError(SpecificResponder.java:71)
at org.apache.avro.ipc.Responder.respond(Responder.java:167)
at
org.apache.avro.ipc.NettyServer$NettyServerAvroHandler.messageReceived(NettyServer.java:158)
at
org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
at
org.apache.avro.ipc.NettyServer$NettyServerAvroHandler.handleUpstream(NettyServer.java:143)
at
org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
at
org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:783)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
at
org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:321)
... snip ...
at java.lang.Thread.run(Thread.java:662)
> 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
