I'm configuring everything directly at the SelectorThread API using examples
like GrizzlyWebServer.java, GrizzlyEmbeddedHttp.java etc.
Ray
On Tue, Mar 30, 2010 at 9:22 AM, Oleksiy Stashok <Oleksiy.Stashok_at_sun.com>wrote:
> Hi Ray,
>
> in Grizzly we don't turn on standard socket keepalive mechanism, but use
> our own (via SelectionKeyHandler API).
>
> If you'd share your Grizzly initialization code - I'll help to change keep
> alive settings.
>
> WBR,
> Alexey.
>
>
>
> On Mar 30, 2010, at 14:12 , Ray Racine wrote:
>
> I notice a number of KeepAlive values in Grizzly, however, I've been
>> unable to find where in Grizzly at the socket level where Socket s,
>> s.setKeepAlive (true) is invoked. My use case is to prevent the NAT from
>> timing out an idle TCP/IP connection.
>>
>> In this case I'm seeking to sustain a dedicated connection between client
>> and server with basic HTTP req/resp. I'd like to set the socket TCP keep
>> alive but I don't see where to do it.
>>
>> Thanks,
>>
>> Ray
>>
>> --
>> The object of life is not to be on the side of the majority, but to escape
>> finding oneself in the ranks of the insane. - Marcus Aurelius
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
--
The object of life is not to be on the side of the majority, but to escape
finding oneself in the ranks of the insane. - Marcus Aurelius