[ https://issues.apache.org/jira/browse/AVRO-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Baldassari updated AVRO-842: ---------------------------------- Attachment: AVRO-842-v3.patch Here's v3 of the patch which fixes the issue with the Netty worker thread pool not closing when NettyTransceiver.close() is called. > 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: 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