| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Java CA client beacon/search timing issues |
| From: | "Kasemir, Kay via Core-talk" <core-talk at aps.anl.gov> |
| To: | "Konrad, Martin" <konrad at frib.msu.edu>, "core-talk at aps.anl.gov" <core-talk at aps.anl.gov> |
| Cc: | Michael Davidsaver <mdavidsaver at ospreydcs.com>, "'Shroff, Kunal'" <shroffk at bnl.gov>, "Sinclair, John" <sinclairjw at ornl.gov> |
| Date: | Fri, 9 Oct 2020 16:14:51 +0000 |
|
>> The consecutive time stamps in the beacon message, however, have an
>> inter-beacon distance of 1992ms, 2930, 2003, 3128, 1989, 2999, 2001, ...
>That doesn't sound right to me. Does casw report beacon anomalies? Yes, it does.
The beacons are indeed sent like that, casw also sees them.
For some reason, though, it doesn't wake up the searches from C-based CA clients to the same extend.
I would love to argue: Look, casw sees irregular beacons from all these IOCs, so fix them.
Instead I hear: The java clients are breaking the control system, and need to fix that.
-Kay
|