From e24954068a6ead31745e4675b294eb6eff964652 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Nicoll?= Date: Mon, 20 Nov 2023 16:24:17 +0100 Subject: [PATCH] Polish --- .../modules/ROOT/pages/integration/checkpoint-restore.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/framework-docs/modules/ROOT/pages/integration/checkpoint-restore.adoc b/framework-docs/modules/ROOT/pages/integration/checkpoint-restore.adoc index 184617df010..7c928644537 100644 --- a/framework-docs/modules/ROOT/pages/integration/checkpoint-restore.adoc +++ b/framework-docs/modules/ROOT/pages/integration/checkpoint-restore.adoc @@ -24,7 +24,10 @@ NOTE: If the checkpoint is created on a warmed-up JVM, the restored JVM will be == Automatic checkpoint/restore at startup -When the `-Dspring.context.checkpoint=onRefresh` Java system property is set, a checkpoint is created automatically during the startup at `LifecycleProcessor.onRefresh` level. At this phase, all non-lazy initialized singletons are instantiated, `InitializingBean.afterPropertiesSet` callbacks have been invoked, but not `Lifecycle.start` ones and `ContextRefreshedEvent` has not yet been published. +When the `-Dspring.context.checkpoint=onRefresh` Java system property is set, a checkpoint is created automatically during +the startup at `LifecycleProcessor.onRefresh` level. At this phase, all non-lazy initialized singletons are instantiated, +`InitializingBean#afterPropertiesSet` callbacks have been invoked, but the lifecycle has not started and +`ContextRefreshedEvent` has not yet been published. WARNING: As mentioned above, and especially in use cases where the CRaC files are shipped as part of a deployable artifact (a container image for example), operate with the assumption that any sensitive data "seen" by the JVM ends up in the CRaC files, and assess carefully the related security implications.