We currently have an application running under R3.13.4 in which there is a
tightly coupled 20 Hz loop between two systems. The CA client, running on
solaris, receives monitors at 20 Hz, and the does some calculations and
returns a demand to the CA server (running on a Heurikon baja68k board) -
for total of 40 CA transactions/second.
About 2-4 times a day Channel Access reports a disconnect in the solaris
client. However, as far as we can see with a network sniffer, the traffic
continues to flow in both directions - the monitors certainly keep on
coming in since the code processes, and it needs the monitors to trigger
this. Nothing appears in the iocLogServer log file.
Has this been seen by anyone else and/or has it bee fixed since R3.13.4? I
have looked at the release notes up to R3.13.8 and find some things which
are maybe close, but most seem to be IOC issues, not client ones.
Cheers,
--
Nick Rees
Head of Software and Computing Services
Joint Astronomy Centre Ph: +1 (808) 961-3756
660 N. Aohoku Place Fax: +1 (808) 961-6516
Hilo, HI. 96720 Email: [email protected]
- Replies:
- RE: Channel Access disconnect/reconnect Jeff Hill
- Navigate by Date:
- Prev:
Re: how to prevent ioc app from being built for both target and host? Till Straumann
- Next:
Re: recDynLink.c for R3.14.1 ? Tim Mooney
- 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: epicsMutexLockWithTimeout not supported in 3.14.1 Kay-Uwe Kasemir
- Next:
RE: Channel Access disconnect/reconnect Jeff Hill
- 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
|