This PR adds a stop event to the thread running the NATS callback to allow the historical data processing service to crash if the service encounters an uncaught exception while processing a rosbag.
Description
Since the nats callback is happening on a separate background thread, currently it remains active even if thread running the rosbag processor part of the service has crashed. This allows users to send new requests which cannot be handled.
The resolution is to allow the service to crash completely, the container is configured to restart indefinitely which will allow the service start up cleanly after the crash.
PR Details
This PR adds a stop event to the thread running the NATS callback to allow the historical data processing service to crash if the service encounters an uncaught exception while processing a rosbag.
Description
Since the nats callback is happening on a separate background thread, currently it remains active even if thread running the rosbag processor part of the service has crashed. This allows users to send new requests which cannot be handled. The resolution is to allow the service to crash completely, the container is configured to restart indefinitely which will allow the service start up cleanly after the crash.
Related GitHub Issue
https://github.com/usdot-fhwa-stol/cda-telematics/issues/196
https://github.com/usdot-fhwa-stol/cda-telematics/issues/188
Related Jira Key
https://usdot-carma.atlassian.net/browse/WFD-545 https://usdot-carma.atlassian.net/browse/WFD-537
Motivation and Context
How Has This Been Tested?
Integration tested
Types of changes
Checklist: