EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024  Index 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: Java CA client beacon/search timing issues
From: Ralph Lange via Core-talk <core-talk at aps.anl.gov>
To: EPICS Core Talk <core-talk at aps.anl.gov>
Date: Sat, 10 Oct 2020 11:10:04 +0200
While the beacons are doing generally well for discovering new IOCs and to recognize flaky network connections, I think the requirement for the client side of having a faster way to detect disconnection of an existing TCP circuit is valid.

What about...
One additional environment variable (Andrew decides the name), configuring the period between alive checks that a client runs against every server that it is connected to. (If the variable is not set, the behavior is unchanged.)
At that period, the client checks for every TCP circuit if any message has been received on that circuit since the last time. If yes, a new "alive" message is sent to the server, if not, the connection is declared to be dead.
Configurable reliable detection, simple implementation, minimal added complexity or network traffic.
Kay runs productional tests in the Java client. If it works, we'll extend it to the C/C++ client.

This way or another, I think such a feature should be additional, compatible with older servers, configurable, only affect the client and not require any changes in the server.

Cheers,
~Ralph

References:
Java CA client beacon/search timing issues Kasemir, Kay via Core-talk
Re: Java CA client beacon/search timing issues Michael Davidsaver via Core-talk
Re: Java CA client beacon/search timing issues Johnson, Andrew N. via Core-talk
Navigate by Date:
Prev: Re: Java CA client beacon/search timing issues Johnson, Andrew N. via Core-talk
Next: Re: Java CA client beacon/search timing issues Michael Davidsaver via Core-talk
Index: 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: Java CA client beacon/search timing issues Johnson, Andrew N. via Core-talk
Next: Re: Java CA client beacon/search timing issues Michael Davidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024 
ANJ, 11 Oct 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·