Spring Boot无法从application.properties加载数据库用户名问题

Hey Eric, I’ve run into exactly this kind of head-scratcher after resetting local databases—let’s break down what might be going wrong and how to fix it:

1. Verify Your MySQL User Exists & Has Proper Permissions #

When you reset your database, it’s easy to misconfigure the rebuilt user without realizing it. Here’s how to check:

• Open EasyPHP’s phpMyAdmin and log in as the root user.
• Run this query to confirm your app’s user exists and has the correct host access:

  SELECT User, Host FROM mysql.user;
  

  Make sure your username shows up, and the Host is set to localhost (or % if you allow remote connections—localhost is safer for local dev).
• Next, check if the user has the necessary permissions to connect and interact with your database:

  SHOW GRANTS FOR 'your-username'@'localhost';
  

  Look for grants like GRANT ALL PRIVILEGES ON your-db-name.* TO 'your-username'@'localhost';—if missing, run this to fix it:

  GRANT ALL PRIVILEGES ON your-db-name.* TO 'your-username'@'localhost';
  FLUSH PRIVILEGES;
  

2. Double-Check Your application.properties Configuration #

Even if you think it’s correct, small typos or overrides can break things:

• Ensure you’re using the exact property name: spring.datasource.username (not user or db-username—Spring Boot is strict about these).
• If your password has special characters (like #, !, or $), wrap it in double quotes to avoid parsing issues:

  spring.datasource.password="your-password-with-special-chars"
  

• Check your app’s startup logs for lines containing spring.datasource.username—this will show you the actual value being loaded, in case environment variables or active profiles are overriding your config.

3. Ensure Hibernate Isn’t Overriding Datasource Settings #

If you have a hibernate.cfg.xml file or are manually setting Hibernate properties, these might take precedence over Spring Boot’s auto-config:

• Open your Hibernate config file and remove any lines like <property name="hibernate.connection.username">...</property> or <property name="hibernate.connection.password">...</property>. Let Spring Boot handle datasource management instead.
• If you need to keep Hibernate-specific config, make sure the username/password there matches exactly what’s in application.properties.

4. Clear Caches & Restart Everything #

Stale connections or cached configs are often the hidden culprit:

• Stop your Spring Boot app, then restart the MySQL service in EasyPHP.
• Clean your project’s build artifacts to eliminate stale compiled code:
  • For Maven: Run mvn clean install
  • For Gradle: Run gradle clean build
• Restart your Spring Boot app and test the connection again.

5. Test the Connection Outside Your App #

Rule out database-side issues by using a tool like DBeaver or phpMyAdmin to connect with the exact same credentials (username, password, database name, host) as your app. If this fails, the problem is definitely with your MySQL user setup—not your Spring Boot code. If it works, you know the issue lies in your app’s config or caching.

内容的提问来源于stack exchange，提问作者Eric