Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: RE: Possible to close a TCP/IP socket in asyn?
From: Mark Rivers <rivers@cars.uchicago.edu>
To: Adam Bark <Adam.Bark@diamond.ac.uk>, Eric Norum <eric@norum.ca>
Cc: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Thu, 23 Oct 2014 17:55:48 +0000
Hi Adam,

What sequence of calls did you make?

You must do the following:

   asynUser *pasynUser;

   status =  pasynCommonSyncIO->connect(port, addr, &pasynUser, drvInfo);
...

  status = pasynCommonSyncIO->disconnectDevice(pasynUser);


It sounds like perhaps you did not call pasynCommonSyncIO->connect first?  Note that you CANNOT use a pasynUser that has been created and connected with any other method except pasynCommonSyncIO->connect().

Mark


________________________________
From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Adam Bark [Adam.Bark@diamond.ac.uk]
Sent: Thursday, October 23, 2014 10:46 AM
To: Eric Norum
Cc: tech-talk@aps.anl.gov
Subject: Re: Possible to close a TCP/IP socket in asyn?

I probably should have checked the return value from asynCommonSyncIO::disconnectDevice before, I'm getting an asynError and the asynUser::errorMessage is "asynManager::queueRequest no processCallback"

On 23/10/14 16:32, Adam Bark wrote:
I didn't but disabling doesn't appear to make a difference, the local port number doesn't change so it is not reconnecting anyway.

On 23/10/14 15:25, Eric Norum wrote:
Do you have autoconnect disabled?

On Oct 23, 2014, at 5:29 AM, Adam Bark <Adam.Bark@diamond.ac.uk<mailto:Adam.Bark@diamond.ac.uk>> wrote:

...
Thanks Mark, that certainly clarifies the situation however if I use asynCommonSyncIO::disconnectDevice (the documentation says this calls asynCommon::disconnect) the socket still shows up as "ESTABLISHED" in netstat, at least with 4-22. Am I missing some incantation? I am unclear what should go in drvPvt if I am to use asynCommon::disconnect directly.

Thanks,
Adam.
--
Eric Norum
eric@norum.ca<mailto:eric@norum.ca>









--

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom







--

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom




Replies:
Re: Possible to close a TCP/IP socket in asyn? Adam Bark
References:
Possible to close a TCP/IP socket in asyn? Adam Bark
RE: Possible to close a TCP/IP socket in asyn? Mark Rivers
Re: Possible to close a TCP/IP socket in asyn? Adam Bark
Re: Possible to close a TCP/IP socket in asyn? Eric Norum
Re: Possible to close a TCP/IP socket in asyn? Adam Bark
Re: Possible to close a TCP/IP socket in asyn? Adam Bark

Navigate by Date:
Prev: Re: Possible to close a TCP/IP socket in asyn? Adam Bark
Next: Focus deadlock Specht, Eliot D.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: Possible to close a TCP/IP socket in asyn? Adam Bark
Next: Re: Possible to close a TCP/IP socket in asyn? Adam Bark
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·