Skip to content

Make SmartLifecycle phase value configurable in STOMP message handling components #32205

New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom
Closed
rstoyanchev opened this issue Feb 6, 2024 · 0 comments
Closed

Make SmartLifecycle phase value configurable in STOMP message handling components #32205

rstoyanchev opened this issue Feb 6, 2024 · 0 comments
Assignees
@rstoyanchev
Labels
in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement
Milestone
6.1.4

Comments

@rstoyanchev
Copy link
Contributor

As per #27519 (comment), these components end up starting after Boot's WebServerStartStopLifecycle, and that creates the possibility for WebSocket connections to be established and messages to start coming before the components are ready.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@rstoyanchev rstoyanchev

Labels
in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement
Projects
None yet
Milestone
6.1.4
Development

No branches or pull requests
1 participant
@rstoyanchev