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
CRaC restoration fails when Actuator's running on a separate port #38502
Comments
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
Nov 22, 2023
This can be reproduced with
Resulting failure:
The restart of the main web server causes the management context, including its web server, to be refreshed again. |
wilkinsona
changed the title
CRaC restoration fails with a custom management port
CRaC restoration fails when Actuator's running on a separate port
Nov 22, 2023
wilkinsona
added
type: bug
A general bug
and removed
status: waiting-for-triage
An issue we've not yet triaged
labels
Nov 22, 2023
Thanks for the quick fix @wilkinsona, I confirm this fixes the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As reported originally on sdeleuze/spring-boot-crac-demo#3, restoration with
spring-boot-starter-actuator
is fine with the default configuration but fails with a custom management port.To reproduce:
management.server.port=8888
tosrc/main/resources/application.properties
./checkpoint.sh
then./restore.sh
The text was updated successfully, but these errors were encountered: