You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
When an application crashes, it can happen that a service is only partially removed and becomes unusable.
An internal service and/or a command line application shall cleanup the remainders of such services.
The following use cases shall be considered:
remove static service info, when only the dynamic service info exists
remove dynamic service info, when only the static service info exists
remove the data segment of a publisher if the owning process no longer exists
remove the publisher/subscriber as participant from the dynamic service info when the owning process no longer exists.
The text was updated successfully, but these errors were encountered:
Could this be done on the startup of the application?
Yes. The basic idea would be to implement a "function" that does it in a thread-safe manner and then either everyone can do this in a decentral fashion or one central daemon or command line tool does this.
This is then up to the deployment/user.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Brief feature description
When an application crashes, it can happen that a service is only partially removed and becomes unusable.
An internal service and/or a command line application shall cleanup the remainders of such services.
The following use cases shall be considered:
The text was updated successfully, but these errors were encountered: