[
https://issues.apache.org/jira/browse/AVRO-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Dumon updated AVRO-754:
-----------------------------
Attachment: nettytransceiver-custom-channelfactory-patch.txt
> NettyTransceiver: allow to provide custom ChannelFactory
> --------------------------------------------------------
>
> Key: AVRO-754
> URL: https://issues.apache.org/jira/browse/AVRO-754
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.5.0
> Reporter: Bruno Dumon
> Attachments: nettytransceiver-custom-channelfactory-patch.txt
>
>
> The threads created by NettyTransceiver are non-daemon threads. The effect is
> that in client apps you need to properly call NettyTransceiver.close() or it
> will hang when done.
> In order to be able to control the kinds of threads (and thread pools) used,
> the attached patch allows to pass the ChannelFactory via the constructor.
> Alternatively, I'd also be happy with the ability to pass the ThreadFactory
> or the ExecutorService, or by making daemon threads the default.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
