>
> As I recall, the crux of this issue is that a shutdown procedure for the
> db
> ca link code would need to destroy all of its channels first, before
> destroying the ca context, and that would require that the individual
> records have shutdown procedures in place also - a big change.
>
Typically there isn't a problem if the ca context is destroyed and the
channels are not deleted first. However in an IOC context we have in memory
channels and the situation is more complex. In that situation if the
channels are not destroyed before the ca context is destroyed we will
continue to receive monitor callbacks as the scan tasks run, and the monitor
callbacks crash when using a ca context that no-longer exists.
I further recall that this could be fixed if:
O CA were to keep a list of all in-memory channels
O When the context is destroyed we could run this list of in-memory channels
and uninstall all of their subscriptions
This would cause some duplication (wasted storage) however because the
database is already storing pointers to all of the channels that it creates,
and presumably we will never get shutdown fixed properly until the db has
implemented an orderly shutdown.
Jeff
- References:
- RE: C++ Exceptions from CAC-UDP on exit Jeff Hill
- Navigate by Date:
- Prev:
RE: C++ Exceptions from CAC-UDP on exit Jeff Hill
- Next:
Re: C++ Exceptions from CAC-UDP on exit Andrew Johnson
- Index:
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: C++ Exceptions from CAC-UDP on exit Jeff Hill
- Next:
Re: C++ Exceptions from CAC-UDP on exit Andrew Johnson
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|