docs: document license-check Java prefs workaround#5585
Open
mcollovati wants to merge 1 commit into
Open
Conversation
The Vaadin license checker uses the Java `Preferences` API during license validation. In hardened environments where the JVM user has no writable home directory -- for example, a locked-down Tomcat service user on Linux -- the JVM repeatedly logs "Could not lock User prefs" warnings. Add a troubleshooting entry under the License documentation that describes the symptom and the standard JVM workaround: setting the `-Djava.util.prefs.userRoot` system property to a writable directory. The entry also notes that Windows and macOS use different backing stores and aren't affected.
Preview DeploymentThis PR has been deployed for preview. URL: https://docs-preview-pr-5585.fly.dev Built from e6e0fe1 |
github-project-automation
Bot
moved this to 🔎Iteration reviews
in Vaadin Flow | Hilla | Kits ongoing work
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Vaadin license checker uses the Java
PreferencesAPI during license validation. In hardened environments where the JVM user has no writable home directory -- for example, a locked-down Tomcat service user on Linux -- the JVM repeatedly logs "Could not lock User prefs" warnings.Add a troubleshooting entry under the License documentation that describes the symptom and the standard JVM workaround: setting the
-Djava.util.prefs.userRootsystem property to a writable directory. The entry also notes that Windows and macOS use different backing stores and aren't affected.