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.
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Assignee||Bruno Dumon [ bruno ]|
|Fix Version/s||1.5.0 [ 12315282 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|23d 10h 39m||1||Doug Cutting||24/Feb/11 22:54|
|15d 1h 38m||1||Doug Cutting||12/Mar/11 00:32|