[
https://issues.apache.org/jira/browse/AVRO-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054560#comment-13054560
]
James Baldassari commented on AVRO-842:
---------------------------------------
I reproduced this in trunk (thanks for the test!), and I assume it's a problem
in the 1.5 branch as well. I'll see if I can put together a patch to fix this
issue as I've recently done some work on the Netty server and transceiver.
> Internal NPE when accessing proxy to a closed server endpoint
> -------------------------------------------------------------
>
> Key: AVRO-842
> URL: https://issues.apache.org/jira/browse/AVRO-842
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.5.1
> Environment: generic
> Reporter: Holger Hoffstätte
> Attachments: CrashTest.java
>
>
> For development of an avro-based transport for remote OSGi services I had to
> wrap & unwind transport-level exceptions into proper exceptions thrown to a
> client. One such scenario is accessing a disconnected/dead endpoint, which
> should be a detectable condition. This works fine with the
> SaslSocketTransceiver (where my wrapper can properly detect the IO
> Exception), but not with Netty which hiccups with an internal NPE.
> Generally speaking any transport-level and remote-endpoint exceptions must
> not only be clearly detectable (either directly by client code or wrapper
> infrastructure around avro) but also distinguishable from another.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
