Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!ucsd!ucbvax!rhino.ncsl.nist.gov!tebbutt
From: tebbutt@rhino.ncsl.nist.gov (John Tebbutt)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re:  Connections that are never released
Message-ID: <9011131652.AA08685@rhino.ncsl.nist.gov>
Date: 13 Nov 90 16:52:29 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: National Institute of Standards and Technology (NIST)
Lines: 15

Peter,

We have been experiencing similar problems with ISODE connections. If a process
goes down, we have to kill all other processes that were connected to it before
we can restart the process. Even then, it can take several attempts before the 
"congestion at TSAP" clears and the process will run.

I have done no research into this at present, deciding instead to put up with it
as an inconvenience for the time being, but like you I would be very interested
to hear from anybody who has an explanation. Is this a non-issue ? Should we be
expecting such behavior ? Does anybody else regard this as a problem ?

	In eager anticipation,

		JT