Geoff,
What are the symptoms of your put failure? I need to know whether it was a "CA
disconnect" related issue as your subject line mentions or a "write failure" as
your message text mentioned. If the circuit was already disconnected when you
initiated the put request then you would receive immediate failure status
indicating that the channel was not connected. Are you making ordinary put
requests or put notify requests? If it was a put notify request, was your
callback handler called with failure status? Otherwise, was a disconnect
callback handler called? Or perhaps an exception handler associated with an
ordinary put request failure was called? Does this application call
ca_pend_xxx() or ca_flush_io() after issuing the last put request? If it was a
write failure then please send any specific status codes or messages that you
see.
o What version of EPICS is in your IOC
o What version of EPICS is in your CA client
Jeff
> -----Original Message-----
> From: Geoff Savage [mailto:[email protected]]
> Sent: Monday, June 02, 2003 10:00 AM
> To: '[email protected]'
> Subject: channel access disconnects
>
> Hi,
>
> I'm trying to understand the cause of sporadic but consistent CA write
> failures. The records in question are typically written every few hours
> and are spread across 12 IOCs. I have not been able to identify a
> pattern with the with failures in terms of one write failing
> consistently.
>
> About a month ago I did discover that the client that writes to these
> records was not calling CA poll at least every 15 seconds as specified
> in the CA manual. For the last month the client calls CA poll once a
> second and the problems persist.
>
> Any suggestions on where to look?
>
> Thanks
>
> Geoff
- References:
- channel access disconnects Geoff Savage
- Navigate by Date:
- Prev:
Re: multicast storms, or how do WRS SPRs work Andrew Johnson
- Next:
RE: bug in VxWorks memPartInfoGet (used by VxStats) 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
- Navigate by Thread:
- Prev:
channel access disconnects Geoff Savage
- Next:
VxWorks on x86 John Sinclair
- 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
|