Uncaught Exception in KS! Thread fix?

[ArmstKP]

Periodically, we receive the "Uncaught Exception in KS! Thread" error in our logs for different RT analytics, which always stops flow of data downstream and no data is outputted in a Real Time Analytic.  The easy fix to this is manually stopping the analytic and restarting.  The larger issue is that if one isn't constantly monitoring errors, the outputting of data stops for days until it is noticed.

Is it possible on the back end to automatically stop and restart the analytic when this error occurs, since this is the easy solution 9 out of 10 times?

[PeterNasuti]

Hi @ArmstKP addressing this is part of related architecture changes for ArcGIS Velocity - thank you for submitting this. Instead of automatically planning to stop and restart we plan to address at a deeper level to prevent the issue from occurring. 

[Teresa_Blader]

Hi @PeterNasuti should we be reporting anytime these "* Uncaught Exception in KS! Thread:" errors show up and we have to stop and restart? Or does the Velocity team see when those occur too?

[PeterNasuti]

@Teresa_Blader Hi Teresa, please log an Esri Support case whenever that message is witnessed so we can address this. Depending on what is found in troubleshooting, the product team may get involved to help provide a resolution.

[Teresa_Blader]

@PeterNasuti Did that! Case number #03809443