Hi again,
Earlier I wrote:
> Your 'casr 2' is being run at a much higher priority than the other Channel
> Access activities. I suspect your CPU is too busy handling higher priority
> operations to spend any time actually running the low-level CA threads that
> communicate with client.
To finish my theory of what's happening here...
When 'casr 2' is run from the shell it goes through each of the client
connections in turn and takes a mutex for the channel. If the mutex is
already owned by a thread that is otherwise CPU-starved, the act of taking the
mutex triggers the vxWorks thread priority inversion protection and raises the
priority of the thread that owns the mutex up to the shell's priority. This
gives it a chance to actually run and complete what it was trying to do.
That's why I think your 'casr 2' causes the duplicate circuits to get cleaned
up properly.
- Andrew
--
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte
- References:
- Runaway connection count on IOC michael.abbott
- Re: Runaway connection count on IOC Andrew Johnson
- Navigate by Date:
- Prev:
Re: Runaway connection count on IOC Andrew Johnson
- Next:
RE: Runaway connection count on IOC Hill, Jeff
- 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: Runaway connection count on IOC Andrew Johnson
- Next:
RE: Runaway connection count on IOC -- Possible Gateway Issue? michael.abbott
- 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
|