Also, are you specifying the IP address as a number or a DNS name? Perhaps the problem is in your DNS lookup rather than in the connect() call.
and does this problem go away with R4-19?
On Jun 2, 2012, at 6:30 AM, Mark Rivers wrote:
>> That's what I was hoping to do too, but I'm not getting a return from the writeRead function.
>> It blocks forever (at least, more than 15 mins) if I attempt a writeRead using the un-connected IP port.
>> Eric suggested this might be due to the operating system timeout on TCP connections (which I gather can be fixed to infinite).
>
> Was that IP port ever connected while this IOC was running? Or was it always unavailable?
>
> Mark
>
> ________________________________________
> From: [email protected] [[email protected]] on behalf of [email protected] [[email protected]]
> Sent: Friday, June 01, 2012 10:45 AM
> To: [email protected]
> Cc: [email protected]
> Subject: RE: asynManager isConnected
>
> Thanks Lewis, Mark and Eric,
>
>>
>> I don't know of a function in Asyn that allows one to determine
>> whether the IP socket is connected. I always just determine
>> this based on the asynStatus returned from a read or write. But
>> maybe there's a way that I don't know about?
>>
>>
>
> That's what I was hoping to do too, but I'm not getting a return from the writeRead function. It blocks forever (at least, more than 15 mins) if I attempt a writeRead using the un-connected IP port. Eric suggested this might be due to the operating system timeout on TCP connections (which I gather can be fixed to infinite).
>
> I'm probably doing something wrong, because I have the asynManager isConnected problem too.
>
> The reason I'm interested in understanding this, rather than just working around it, is because I want to handle connections to ethernet PMAC motor controllers automatically if they come up *after* the IOC has already started. Currently we have to restart an IOC if any of our PMACs come up that were turned off when the IOC was started.
>
> Cheers,
> Matt
>
> --
> 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
>
>
>
>
>
>
--
Eric Norum
[email protected]
- References:
- asynManager isConnected matthew.pearson
- Re: asynManager isConnected J. Lewis Muir
- RE: asynManager isConnected matthew.pearson
- RE: asynManager isConnected Mark Rivers
- Navigate by Date:
- Prev:
RE: asynManager isConnected Mark Rivers
- Next:
RE: asynManager isConnected Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: asynManager isConnected Mark Rivers
- Next:
RE: asynManager isConnected Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|