-
Notifications
You must be signed in to change notification settings - Fork 40.6k
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
Graceful shutdown for RSockets #25399
Labels
status: blocked
An issue that's blocked on an external project change
type: enhancement
A general enhancement
Milestone
Comments
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
Feb 23, 2021
Isn't this blocked by the RSocket issue you referenced? |
I suppose. TBH I don't know. We'd have to ask @OlegDokuka. |
bclozel
added
the
status: blocked
An issue that's blocked on an external project change
label
Mar 2, 2021
wilkinsona
added
type: enhancement
A general enhancement
and removed
status: waiting-for-triage
An issue we've not yet triaged
labels
Jan 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
status: blocked
An issue that's blocked on an external project change
type: enhancement
A general enhancement
Along the lines of
WebServer.shutDownGracefully()
it would be good to be able to control the shutdown of an RSockets app (client and server). Right now, I think all you can do isApplicationContext.close()
and that leads to potentially cutting off in-flight requests and channels at the knees. See also: rsocket/rsocket-java#988.The text was updated successfully, but these errors were encountered: