Re: about not releasing network connection

Hi Cliffsman,

On Wed, Nov 03, 2004 at 11:18:51AM +0800, masculinedragon wrote:
> hello,
> i am using ob4.1.0 in the poor network link where client and server 
> terminal installed with 100M ethernet card, but there is a 64kbps link with 
> high code error happenning in the whole client-to-server link. 
> 
> we are using windows2000 paltform.
> 
> we define 
>   interface hello
>   {
>      void say_hello(in string data)
>   };
> 
> client wants to send 1MB size data to server with timeout 10 seconds. 
> if there is timeout, then client decrease the data to half and reconnect, 
> and so on until having sent 1MB. because link is poor, so it expires so often 
> even if data size just is 1000 bytes. we judge timeout through no_response 
> excetion. but we find the connection between client and server is not 
> released when catching no_response excetion, even if the client process 
> have exited. 
> 
> i am confused with this phenomena, is it caused by ob or windows os??????
> 
> thanks.
> cliffsman

Hmm, if the client process terminates, then the TCP connection should
eventually terminate.  Often with the socket handler (in your case on
the server-side) it will enter a TIME_WAIT state:  in this state it will
keep the socket open for a period of time (1 or 2 minutes) in order to
receive any data that the client may have sent before it shutdown.  On
Windows 2000 machines I believe this value is 240 seconds by default.
If this what you are seeing?  (A 'netstat' should give you this
information.)

Cheers.

-- 
Dion Picco, Software Engineer
IONA Technologies Inc.
Team Orbacus - Your CORBA Source
mailto:[email protected]
http://www.orbacus.com
_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html