Gradle运行含CrudRepository与MySQL的Java项目启动失败求助

Hey there! Let's dig into why your Spring Boot (I assume it's Spring Boot since you're using bootRun and CrudRepository) app is failing to start even after Gradle builds successfully. Since you've already checked the basic DB credentials and URL, let's go through some less obvious but common culprits:

1. Double-check if your target database exists #

Even if your URL is formatted correctly, if the database name specified in spring.datasource.url (the part after the final /, like jdbc:mysql://localhost:3306/your_db_name) doesn't exist in MySQL/PHPMyAdmin, the app will fail to connect. Head into PHPMyAdmin to confirm the exact DB name matches what's in your config. If it's missing, you can either create it manually, or add spring.sql.init.mode=always to your application.properties to let Spring Boot auto-create it on startup.

2. Verify MySQL driver version compatibility #

Make sure the MySQL driver in your build.gradle matches your MySQL server version. For MySQL 8+, you need the newer connector dependency—older drivers will throw authentication or connection errors. Your dependency should look something like this:

implementation 'com.mysql:mysql-connector-j:8.0.33'

If you're on an older MySQL version (5.x), use mysql:mysql-connector-java:5.1.49 instead.

3. Dig into the full stack trace for specific errors #

Don't just glance at the final failure message in IntelliJ's Run console—scroll up to find the root cause. Common red flags here include:

• Access denied for user 'your_user'@'localhost': Even if credentials are correct, the user might not have permission to connect from localhost (sometimes users are configured for % (any host) but not localhost specifically).
• Unknown database 'your_db': Confirms the database doesn't exist (tie back to step 1).
• SSL connection error: MySQL 8 enables SSL by default for local connections sometimes. Add ?useSSL=false to your datasource URL (only for local debugging—don't use this in production) to bypass it.

4. Check for JPA/Hibernate configuration mismatches #

Since you're using CrudRepository, Spring Data JPA is handling your DB interactions. Make sure your application.properties has the right dialect and DDL settings:

spring.jpa.hibernate.ddl-auto=update
spring.jpa.properties.hibernate.dialect=org.hibernate.dialect.MySQL8Dialect
spring.jpa.show-sql=true

Using the wrong dialect (like MySQL5Dialect with MySQL 8) can cause schema initialization failures.

5. Confirm MySQL server is running #

It sounds obvious, but it's easy to overlook! If PHPMyAdmin loads without issues, your server is up. If not, check your OS's service manager:

• Windows: Open services.msc and look for the MySQL service.
• Linux: Run systemctl status mysql in the terminal.

6. Clean and rebuild your project #

Cached build files can sometimes cause weird inconsistencies. Run ./gradlew clean bootRun (or gradlew clean bootRun on Windows) to wipe the Gradle cache and start fresh. You can also invalidate IntelliJ's caches by going to File > Invalidate Caches... and restarting the IDE.

Once you spot the specific error from the stack trace, that'll point you straight to the fix. If you find a particular error message you can't parse, feel free to share it and we can narrow it down further!

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