| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: 'CAS-client' failed in ../db/dbEvent.c line 540 |
| From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "Makarov, Oleg A." <makarov at anl.gov>, "Jeffrey O. Hill" <johill at lanl.gov>, Ralph Lange <Ralph.Lange at bessy.de> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Tue, 6 Sep 2022 20:48:05 +0000 |
|
Hi Oleg, What release of the vxWorks BSP are you using? You can see with the “release” command at the vxWorks prompt. Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Makarov, Oleg A. via Tech-talk Hi Jeffrey and Ralph, I am observing occasional/intermittent error in the vxWorks EPICS IOC. Error occurs during connection from CA client to the PVs in the IOC. mvme6100 IOC is running on EPICS version 7.0.6.1. We have CA clients using Java JCA library 2.4.1 and pyepics 3.5.0. A call to 'assert(status == epicsMutexLockOK)'
by thread 'CAS-client' failed in ../db/dbEvent.c line 540. EPICS Release EPICS R7.0.6.1. Local time is 2022-09-06 14:58:32.719904388 CST/CDT Please E-mail this message to the author or to
tech-talk at aps.anl.gov Calling epicsThreadSuspendSelf() Do you have any insights on how to avoid this error? Thank you, Oleg Makarov and Mark Hillgart |