[
https://issues.apache.org/jira/browse/AVRO-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058069#comment-13058069
]
James Baldassari commented on AVRO-842:
---------------------------------------
Hi Doug,
Yes, this patch should go into 1.5.2. It has some important fixes, and it
should apply cleanly to the 1.5 branch. If Holger has time to test it out one
more time, that would be great, but I'm pretty confident that the most recent
version of the path fixes the issues reported here (and in AVRO-747).
> 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
> Assignee: James Baldassari
> Attachments: AVRO-842-v2.patch, AVRO-842-v3.patch, AVRO-842.patch,
> 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
