On 3/24/09 14:43 , "GaryCarr" <[email protected]> wrote:
> Are there any limitations that apply to one, and not the other?
In case you depend on the exact verbiage of error messages,
they differ. CAJ tends to give more specific ones like
access permission error while JCA might just report write error.
CAJ seems to be perfectly fine with multithreaded access,
while I've run into deadlocks when for example calling JNI JCA
from one thread, trying to remove a monitor, while a JNI JCA
value update arrived on another thread for another PV.
I think Jeff said that the CA client library itself does not
lock in those cases, to the lock might be inside the JNI code,
but in any case you must not lock anything in your code
when dealing with JNI JCA because that can result in deadlocks.
Thanks,
-Kay
- References:
- JCA2 vs CAJ GaryCarr
- Navigate by Date:
- Prev:
JCA2 vs CAJ GaryCarr
- Next:
Re: JCA2 vs CAJ Kasemir, Kay
- 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:
JCA2 vs CAJ GaryCarr
- Next:
Re: JCA2 vs CAJ Kasemir, Kay
- 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
|