Specifying Accept Timeouts on Server Sockets

[Sai Pullabhotla]

Well, that's what I thought, but it did not work. It looks like the
IdleStateHandlers are working only for read and write timeouts, but
not for accept timeouts.

Correct me if I'm wrong, but I think the accept timeouts should be
handled by the parent handler of a Bootstrap, not by the channel
pipeline that the child channels use. Is this correct? Could some one
give me some hints on how to get this working?

2010/8/13 Marc-André Laverdière <marcandre.laverdiere at gmail.com>:
> You could always have a timeout handler.
>
> Marc-André LAVERDIÈRE
> "Perseverance must finish its work so that you may be mature and
> complete, not lacking anything." -James 1:4
> mlaverd.theunixplace.com/blog
>
>  /"\
>  \ /    ASCII Ribbon Campaign
>   X      against HTML e-mail
>  / \
>
>
>
> 2010/8/12 Sai Pullabhotla <sai.pullabhotla at jmethods.com>:
>> Hello,
>>
>> Is there a way to specify accept timeouts on server sockets? For
>> example, an FTP server would typically listen on a random port in
>> response to a PASV command from the client. If for some reason, the
>> client does not open the connection to this passive port in a
>> specified amount of time, I would like to shutdown the listener and
>> free up the port/resources. Java's plain ServerSockets make use of the
>> SO_TIMEOUT methods to achieve this. But, I did not find any equivalent
>> in Netty. Can some one tell me if this is supported and steer me in
>> the right direction?
>>
>> Thanks in advance for your help.
>> Sai.
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/netty-users
>>
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users