Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!xtel.co.uk!c.robbins
From: c.robbins@xtel.co.uk (Colin Robbins)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re: Connections that are never released
Message-ID: <9011141453.AA25231@ucbvax.Berkeley.EDU>
Date: 14 Nov 90 08:37:41 GMT
References: <9011132207.AA03886@rainier.udev.cdc.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 49



   > I also have been writing DUAs etc.  The only way I have found to release 
   > half open connections to the DSA is to have the DUAs xselect their bind
   > connections to the DSA.  That way the DUAs are awakened by the collapse
   > of the bind connections when the DSA fails.  The DUAs can then cleanup
   > the connections.  I don't believe DISH and friends do so.

DISH does not do this.

This is a problem we investigated over a year ago when we first
noticed the problem.  We could find no satisfactory solution.
It would appear that if a client gets into the FIN_WAIT_2 state, and
the server goes away, there is no way that the client can exit cleanly.
(Of course 'kill -9' does the trick!).
I should point out I am not a TCP/IP expert, so this may be totally wrong !


   > Thanks, Jim Reed
   >	 Control Data Corporation

   > PS:  I'm running ISODE-6.6 and have fixed some of the QUIPU leakage in
   >      that release.  I can forward my humble corrections to you if you're
   >      interested.

We beleive that we have fixed all the memory leak problems in Quipu in
the 6.7 release we are using internally.
If you could mail quipu-support details of any changes you have made,
we will take a look to make sure.

I should point out that then is not a significant memory problem in
the 6.0/6.1 versions of Quipu.  The problems were introduced in code
being developed for the 7.0 version of Quipu.

   >      Colin Robbins says he has or will soon post corrections QUIPU.

Details of the 6.1 upgrade, and two other patches have been mailed to
the quipu list since the 6.0 release.
I will resend details to the Quipu list in the next message.

   >      Also, a new version of QUIPU is due soon with such corrections and
   >      "updates" to the QUIPU encoders/decoders.  Perhaps we should wait
   >      for the new versions.  I'm worried though that problems with PEPSY
   >      (the new ASN.1 compiler) could delay the next version.

Time will tell !


Colin