Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unset ForwarderSessionState property after runtime restart #346

Open
rgallor opened this issue Mar 8, 2024 · 0 comments
Open

Unset ForwarderSessionState property after runtime restart #346

rgallor opened this issue Mar 8, 2024 · 0 comments

Comments

@rgallor
Copy link
Collaborator

rgallor commented Mar 8, 2024

If the device runtime suddenly crashes and one or more device forwarder sessions were active, after it has been restarted, it will neither attempt to unset the sessions' state nor to re-establish them.
To prevent this, it is necessary that, when initialized, the device forwarder retrieves the previously stored ForwarderSessionState property values from Astarte. However, this can only be done if the SqliteStore is being used, which can be trivial if the AstarteMessageHub is used instead of the AstarteDeviceSdk. It is necessary to modify the astarte-message-hub-proto and the AstarteMessageHub to enable the correct transmission of the ForwarderSessionState property values to the device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant