dev@grizzly.java.net

Re: About TIME_WAIT remain

From: Bongjae Chang <carryel_at_korea.com>
Date: Tue, 16 Jun 2009 22:14:09 +0900

Hi Jeanfrancois,

Jeanfrancois wrote:
> So I do think we can do something on our side. What do you think?

I think if we can do something, we should do. But I don't know the ways until now though I have tried to do various kinds of trial.

If you find later, please let me know. :)

Thanks.

--
Bongjae Chang


----- Original Message -----
From: "Jeanfrancois Arcand" <Jeanfrancois.Arcand_at_Sun.COM>
To: <dev_at_grizzly.dev.java.net>
Sent: Tuesday, June 16, 2009 12:45 AM
Subject: Re: About TIME_WAIT remain


> Salut,
>
> Bongjae Chang wrote:
>> Hi,
>>
>> When I tested my attached sample, I found that TIME_WAIT connection
>> remained for a while on both Windows and Linux.
>>
>> Test program is very simiple.
>>
>> 1. create a controller with a server TCPSelectorHandler.
>> 2. create a new client socket and connect the server.
>> 3. close the client socket and stop the controller.
>>
>> I don't know why TIME_WAIT state remains though I close both the server
>> and client cleanly.
>>
>> I think you can also reproduce this in some Grizzly's unit test cases
>> which use a TCPIOClient like BaseSelectionKeyHandlerTest.
>>
>> This TIME_WAIT state may be meaningless because Grizzly sets
>> setReuseAddress to be true.
>>
>> But I am curious to know why TIME_WAIT state doesn't disappears fast.
>
> I think this is OS related, e.g the underlying socket will be completely
> destroyed based on some OS configuration. I've Googled the TIME_WAIT and
> found:
>
> http://www.developerweb.net/forum/showthread.php?t=2941
>
> So I do think we can do something on our side. What do you think?
>
> A+
>
> -- Jeanfrancois
>
>
>>
>> Please advice me.
>>
>> Thanks.
>>
>> --
>> Bongjae Chang
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>
>
>