Add server lifecycle participants - #1835
Merged
Merged
Conversation
Provide server-owned components a startup seam after core facilities initialize and before endpoints become externally visible. Ensure deterministic ordering and cleanup across startup and shutdown failures.
kevinherron
marked this pull request as ready for review
August 3, 2026 12:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpcUaServer currently has no supported lifecycle phase for application components that need the standard address space and core event facilities to be ready before any endpoint becomes visible. Components such as AliasManager and application namespaces must otherwise start either too early or after clients can already connect.
This adds a server-owned lifecycle participant API. Registered Lifecycle instances start in order after core initialization and before passive transport binding or reverse-connect startup. The server stops them in reverse order after removing external visibility, rolls back started participants when startup fails, and preserves cleanup failures without replacing the primary failure.
The existing Lifecycle and AbstractLifecycle APIs remain unchanged.