Experimental Physics and Industrial Control System
> Here is a simple test using the EPICS caget
Agree with Andrew that this is a somewhat usual way to use the CA client
library. Nevertheless, the symptoms as reported smells like a bug. I created
mantis entry 306 to tack progress on the issue.
Thanks for documenting the symptoms,
Jeff
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Owens, PH (Peter)
> Sent: Thursday, January 17, 2008 3:54 AM
> To: [email protected]
> Subject: CA connection management problem
>
>
>
> -----Original Message-----
> From: Victor F E Pucknell [mailto:[email protected]]
> Sent: 16 January 2008 15:01
> To: Duggan, AJ (Andrew)
> Cc: Owens, PH (Peter); Letts, SC (Simon)
> Subject: EPICS problem
>
>
>
>
> Here is a simple test using the EPICS caget
> Normally it is in a loop using caget every 2 seconds.
> If you "quit" the EPICS server then I get a serious failure and the
test
> program is lost somewhere in the ca library
>
> Here is the output from the test program
>
> #############
>
> ca_pend_io returned with rc=0x1: value=0x0 ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0 ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0 ca_get returned with rc=0x1
> CA.Client.Exception...............................................
> Warning: "Virtual circuit disconnect"
> Context: "nndhcp069.dl.ac.uk:5064"
> Source File: ../cac.cpp line 1126
> Current Time: Wed Jan 16 2008 14:46:01.574167550
> ..................................................................
> CA.Client.Exception...............................................
> Warning: "Virtual circuit disconnect"
> Context: "op=0, channel=MEIS-B-A-201:STA, type=DBR_SHORT, count=1,
> ctx="nndhcp069.dl.ac.uk:5064""
> Source File: ../getCopy.cpp line 86
> Current Time: Wed Jan 16 2008 14:46:01.574311751
> ..................................................................
> ca_pend_io failed User specified timeout on IO operation expired ca_get
> failed Virtual circuit disconnect EPICS server failure - resetting
>
> A call to "assert (_pTargetMutex == & mutexToVerify)" failed in
> ../../../include/epicsGuard.h line 84.
> EPICS Release EPICS R3.14.9-3.14.9 $R3-14-9$ $2007/02/05 16:31:45$.
> Current time Wed Jan 16 2008 14:46:08.582331945.
> Please E-mail this message to Jeff Hill [email protected] or to tech-
> [email protected] Calling epicsThreadSuspendSelf()
>
>
> #####################
>
> However if kill the EPICS server using Control+C then the application does
> seem to recover and resume once I restart the EPICS server.
>
>
> ##################
>
>
>
>
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> CA.Client.Exception...............................................
> Warning: "Virtual circuit disconnect"
> Context: "nndhcp069.dl.ac.uk:5064"
> Source File: ../cac.cpp line 1126
> Current Time: Wed Jan 16 2008 14:50:41.049109570
> ..................................................................
> CA.Client.Exception...............................................
> Warning: "Virtual circuit disconnect"
> Context: "op=0, channel=MEIS-B-A-201:STA, type=DBR_SHORT, count=1,
> ctx="nndhcp069.dl.ac.uk:5064""
> Source File: ../getCopy.cpp line 86
> Current Time: Wed Jan 16 2008 14:50:41.049255811
> ..................................................................
> ca_pend_io failed User specified timeout on IO operation expired
> ca_get failed Virtual circuit disconnect
> EPICS server failure - resetting
> Attempting start....
> calling ca_context_create
> calling ca_create_channel
> calling ca_pend_io
> ca_pend_io failed User specified timeout on IO operation expired
> Attempting start....
> calling ca_context_create
> calling ca_create_channel
> calling ca_pend_io
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
> ca_get returned with rc=0x1
> ca_pend_io returned with rc=0x1: value=0x0
>
>
> ######################
>
>
> This was not an exhaustive trial. I tried each only a couple of times.
> However the asset failure and the suspend is typical of what we see.
>
> Vic
>
>
- References:
- CA connection management problem Owens, PH (Peter)
- Navigate by Date:
- Prev:
Re: CA connection management problem Andrew Johnson
- Next:
Re: CA connection management problem Maren Purves
- 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: CA connection management - vxWorks David Maden
- Next:
error in communicating to the GPIB device with NI-PCI board zhangdemin99
- 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