Re: about not releasing network connection

Hi Paul,

On Wed, Nov 10, 2004 at 08:39:18AM -0800, Haggerty, Paul wrote:
> I've seen a similar issue with JOB 4.1.3 Client connections hanging around
> even after the client process is terminated. This is a happening with
> Windows 2000 clients and Solaris 8 server. Netstat shows the connection in
> TIME_WAIT state. An easy way to reproduce the problem is to pull the
> ethernet cable on the client machine. On the server the connection never is
> closed.
> 
> I workaround this by using the "ooc.orb.server_timeout" property which
> closes connections that are idle for a defined period of time. 
> 
> If there is a better way to handle this, please let me know.

Unfortunately the TIME_WAIT state happens on the socket layer at the OS
level.  You can change the value for this in the registry on Windows but
the actual socket-based applications have no control over this as far as
I know.  The shutdown procedure for TCP connections is a 3-state process
and unless its completed properly, the socket has no choice but to enter
a TIME_WAIT state in order to receive any outstanding data on the line.
With a proper shutdown procedure this should not occur since either side
is not abruptly terminating.

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