SLCORE-2200 Avoid error in H2: Wrong user name or password#1875
Open
nquinquenel wants to merge 1 commit intomasterfrom
Open
SLCORE-2200 Avoid error in H2: Wrong user name or password#1875nquinquenel wants to merge 1 commit intomasterfrom
nquinquenel wants to merge 1 commit intomasterfrom
Conversation
|
damien-urruty-sonarsource
approved these changes
Mar 18, 2026
Contributor
damien-urruty-sonarsource
left a comment
damien-urruty-sonarsource
left a comment
There was a problem hiding this comment.
I'm not very comfortable trying a blind fix, but let's give it a try
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.
Potential explanation:
When a second instance (e.g. another IDE window) tries to connect to the database, it uses TCP to connect to the initially started H2 server. The H2 driver uses the exact database path string from the JDBC URL as part of the password hashing process.
On OS like Windows where paths are case insensitive, it's possible for different processes to resolve the storage directory with slightly different string casings (e.g. C:... vs c:...). The lock file is read correctly since the file system is case-insensitive, but the TCP connection fails because the hashed password sent by the client (hashed with c:) doesn't match what the server expects (hashed with C:).