Hi Yang, NettyTransceiver tries to automatically reconnect if the connection is lost. Sometimes it gets stuck because no timeout is used on the connection, as you mentioned. Please see this issue for a patch:
https://issues.apache.org/jira/browse/AVRO-943 -James On Mon, Oct 31, 2011 at 1:07 PM, Yang <[email protected]> wrote: > it looks > > NettyTransceiver.getChannel().getChannelConfig().setTimeoutMillis() > could be a possible approach? > > > > On Mon, Oct 31, 2011 at 9:41 AM, Yang <[email protected]> wrote: > > this is more of a problem on TCP itself: if I have a TCP connection > > established, then > > I pull out the network cable, the TCP connection is still on, as soon > > as I re-connect the cable. > > > > in the case of Avro RPC call, if I pull out the cable, the RPC just > > blocks, without throwing an exception. > > I see https://issues.apache.org/jira/browse/FLUME-313 addressing > > this for HTTP transceiver, > > is there a similar patch for NettyTransceiver? > > > > Thanks > > Yang > > >
