users@grizzly.java.net

Re: Grizzly Idle timeout

From: Tigran Mkrtchyan <tigran.mkrtchyan_at_desy.de>
Date: Fri, 15 Oct 2010 12:27:43 +0200

  Hi Keith,

this is what I have in my code:

         DefaultSelectionKeyHandler keyHandler = new
DefaultSelectionKeyHandler();
         keyHandler.setTimeout(-1);

          final TCPSelectorHandler tcp_handler = new TCPSelectorHandler();
          tcp_handler.setPortRange(portRange);
          tcp_handler.setSelectionKeyHandler(keyHandler);


Regards,
    Tigran.
On 10/15/2010 12:14 PM, Keith Shu wrote:
>
> MY first time posting here.
> I'm using Grizzly 1.9.19 to implement a socket server processing TCP
> messages.
> I used the example from echo filter. Everything works great except
> one issue.
> When the client is idle - (not sending any messages) the connection
> terminates after about 2 minutes.
> Is this by design? I've looked at all the timeout settings and keep
> alives but all seems ok to me.
>
> I think you can recreate this by running Echo filter, then open a
> telnet to the port but don't send any message.
> How can i make the connection persist even when there's no message
> passed.
>
> Thanks in advance for responses. Hope it can be prompt.
> Keith
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>