[
https://issues.apache.org/jira/browse/AVRO-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13058260#comment-13058260
]
Holger Hoffstätte commented on AVRO-842:
----------------------------------------
Just gave patch v3 a try and it now works fine. The VM even correctly exits
when the client is not shut down explicitly, since the ExecutorService reaps
its thread after a minute and then cleanly exits. This shows that there are no
accidental leaks. nice :)
> 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
> Fix For: 1.5.2
>
> 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
