Experimental Physics and Industrial Control System
Hi all,
I got a strange effect with ca_sg_put if writing to a record where DISP=1.
The ca_sg_put succeeds (returns ECA_NORMAL) but then,
an error message is printed asynchronously:
CA.Client.Exception...............................................
Warning: "Channel write request failed"
Context: "op=1, channel=DZ-AO3, type=DBR_invalid, count=0, ctx="write
notify request rejected""
Source File: ../syncGroupWriteNotify.cpp line 98
Current Time: Wed Feb 28 2007 16:40:34.421658000
..................................................................
Finally, ca_sg_block times out, long after it was clear to CA that writing failed.
Especially the last point is strange to me. Is this a bug or is it designed this
way?
If it works as intended, what is the correct way to handle failing synchronous
writes to records with DISP=1 without timing out?
I am using R3.14.8.2.
Dirk
--
Dr. Dirk Zimoch
Computing and Controls
Paul Scherrer Institut
phone +41 56 310 5182
fax +41 56 310 4413
- Replies:
- Re: ca_sg_put problem with DISP=1 Andrew Johnson
- Navigate by Date:
- Prev:
task priorities, busy cpu, and timeout Dennis Nicklaus
- Next:
Re: task priorities, busy cpu, and timeout Andrew Johnson
- 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: task priorities, busy cpu, and timeout Korhonen Timo
- Next:
Re: ca_sg_put problem with DISP=1 Andrew Johnson
- 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