Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polish

Browse Source 
See gh-39910
This commit is contained in:
Johnny Lim
2024-03-12 23:23:00 +09:00
committed by Moritz Halbritter
parent 24218ac4a8
commit 412b8dd548
13 changed files with 18 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
spring-boot-project/spring-boot-docs/src/docs/asciidoc/actuator/endpoints.adoc
View File

@@ -1203,7 +1203,7 @@ The `info` endpoint publishes information about your Operating System, see {spri
[[actuator.endpoints.info.process-information]]
==== Process Information
The `info` endpoint publishes information about your process, see {spring-boot-module-api}/info/ProcessInfo.html[`Process`] for more details.
The `info` endpoint publishes information about your process, see {spring-boot-module-api}/info/ProcessInfo.html[`ProcessInfo`] for more details.

2
spring-boot-project/spring-boot-docs/src/docs/asciidoc/deployment/efficient.adoc
View File

@@ -72,7 +72,7 @@ To learn more about ahead-of-time processing, please see the <<native-image#nati
https://wiki.openjdk.org/display/crac/Main[Coordinated Restore at Checkpoint] (CRaC) is an OpenJDK project that defines a new Java API to allow you to checkpoint and restore an application on the HotSpot JVM.
It is based on https://github.com/checkpoint-restore/criu[CRIU], a project that implements checkpoint/restore functionality on Linux.
The principle is the following: you start your application almost as usual but with a CRaC enabled version of the JDK like https://bell-sw.com/pages/downloads/?package=jdk-crac[Bellsoft Liberica JDK with CRaC] or https://www.azul.com/downloads/?package=jdk-crac#zulu[Azul Zulu JDK with CRaC].
The principle is the following: you start your application almost as usual but with a CRaC enabled version of the JDK like https://bell-sw.com/pages/downloads/?package=jdk-crac[BellSoft Liberica JDK with CRaC] or https://www.azul.com/downloads/?package=jdk-crac#zulu[Azul Zulu JDK with CRaC].
Then at some point, potentially after some workloads that will warm up your JVM by executing all common code paths, you trigger a checkpoint using an API call, a `jcmd` command, an HTTP endpoint, or a different mechanism.
A memory representation of the running JVM, including its warmness, is then serialized to disk, allowing a fast restoration at a later point, potentially on another machine with a similar operating system and CPU architecture.

2
spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/ssl.adoc
View File

@@ -80,7 +80,7 @@ When used to secure a client-side connection, a `truststore` is typically config
[TIP]
====
PEM content can be used directly for both the `certificate` and `private-key` properties.
If the property values contains `BEGIN` and `END` markers then they will be treated as PEM content rather than a resource location.
If the property values contain `BEGIN` and `END` markers then they will be treated as PEM content rather than a resource location.
The following example shows how a truststore certificate can be defined:

2
spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/testing.adoc
View File

@@ -1055,7 +1055,7 @@ include::code:MyRedisConfiguration[]
Spring Boot can't tell from `GenericContainer` which container image is used, so the `name` attribute from `@ServiceConnection` must be used to provide that hint.
You can also can use the `name` attribute of `@ServiceConnection` to override which connection detail will be used, for example when using custom images.
You can also use the `name` attribute of `@ServiceConnection` to override which connection detail will be used, for example when using custom images.
If you are using the Docker image `registry.mycompany.com/mirror/myredis`, you'd use `@ServiceConnection(name="redis")` to ensure `RedisConnectionDetails` are created.