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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: asyn timeout |
From: | Mark Rivers <[email protected]> |
To: | "'Pedro Gigoux'" <[email protected]>, Torsten bögershaus <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Mon, 19 Oct 2015 19:10:15 +0000 |
Hi Pedro, It seems like it might be a good idea to add optional keepalive support to the asyn socket driver. If I were to create a branch on github that implemented this would you
be able to test it? Mark From: [email protected] [mailto:[email protected]]
On Behalf Of Pedro Gigoux Hi Torsten, The instrument is located in a remote institution so I don't have much details about their network setup. On our side, the machine where the software runs goes through a couple of switches and the firewall before connecting to the remote
host. Our IP is registered on their firewall to accept connections to the instrument. According to our IT department we don't have timeouts for outgoing traffic so we suspect the remote network equipment is the one dropping the connection (I don't have hard
evidence to support this yet, though). A workaround that has been proposed is to modify the software to send a ping-like packet every minute to prevent the link from going down. Thank you, Pedro. On 19 October 2015 at 12:27, Torsten bögershaus <[email protected]> wrote: Not with asyn in special, but with all kind of TCP/IP related devices.
|