HP3000-L Archives

August 2003, Week 1

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Troubles with Sockets
From:
"Gribbin, Francis J." <[log in to unmask]>
Reply To:
Gribbin, Francis J.
Date:
Tue, 5 Aug 2003 14:19:23 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines) 
Hi Jim,

Looks like the UNISYS machine is acting like a server and the HP3ks are clients that connect and disconnect.  Servers note client disconnects in different ways (eg timeout due to inactivity).  Take a look at the UNISYS documentation to see how this is implemented.

Regards,

Frank Gribbin
Potter Anderson & Corroon LLP

-----Original Message-----
From: JIM McINTOSH [mailto:[log in to unmask]]
Sent: Wednesday, July 30, 2003 11:17 AM
To: [log in to unmask]
Subject: [HP3000-L] Troubles with Sockets


 I am struggling with an application that used NETIPC to establish a outbound
socket to a UNISYS machine.  Even after the application has terminated and
the logon session has terminated, the UNISYS thinks that the connection is
still alive.  Is this possible?  Can an outbound socket become orphaned from
its creator?  Is there a method whereby I can determine what outbound
sockets are currently in use systemwide?  This application is running on 2
HP3000's.  One has 6.0 and one has 6.5.

I appreciate any insight you might be able to provide.

Jim McIntosh

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2