You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2011/02/24 23:54:38 UTC
[jira] Resolved: (AVRO-754) NettyTransceiver: allow to provide
custom ChannelFactory
[ https://issues.apache.org/jira/browse/AVRO-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting resolved AVRO-754.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Assignee: Bruno Dumon
I just committed this. Thanks, Bruno!
> 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
> Assignee: Bruno Dumon
> Fix For: 1.5.0
>
> 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