Hibernate数据库连接失败及事务提交异常问题求助

Hey there, sorry to hear this has been frustrating you for 5 whole days—let’s dig into these two problems and get you back on track.

1. Transaction Commit Exception (Transaction was marked for rollback only) #

This error is a common gotcha with Spring+Hibernate transactions, and the fact it’s happening across multiple projects points to either a consistent configuration mistake or an environment issue. Here’s what to check:

• Uncaught exceptions in transactional code: If any runtime exception (or a checked exception specified in rollbackFor) is thrown inside a @Transactional method and not properly handled, Spring automatically marks the transaction for rollback. Even if you catch the exception later, the rollback flag is already set. Double-check your test methods for patterns like:

  @Transactional
  public void testMethod() {
      try {
          // Code that throws an unhandled exception
      } catch (SomeException e) {
          // No rethrow or transaction status adjustment
      }
  }
  

  If this is the case, you’ll need to either rethrow the exception or use TransactionStatus.setRollbackOnly(false) cautiously (only if you’re sure the exception doesn’t invalidate the transaction state).

• Incorrect @Transactional configuration: Verify your transaction annotations. For example, if you’ve set noRollbackFor to exclude an exception type that’s actually being thrown, or if rollbackFor is missing a checked exception you’re expecting to trigger a rollback.

• Cross-method transaction pitfalls: If you’re calling a @Transactional method from a non-transactional method in the same class, the transaction annotation won’t take effect (due to Spring’s proxy-based AOP). This can lead to unexpected exception handling and rollback marks.

• Environment-level transaction settings: Check your database’s transaction isolation level—some aggressive settings might cause implicit rollbacks. Also, ensure you’re using a compatible Spring+Hibernate version combo; older versions had bugs related to transaction rollback marking in edge cases.

2. Hibernate Database Connection Failure #

This issue often boils down to configuration or environment mismatches. Let’s eliminate the most common culprits:

• Invalid connection parameters: Triple-check your application.properties/application.yml (or Hibernate config file) for typos:

  spring.datasource.url=jdbc:mysql://localhost:3306/your_db?useSSL=false&serverTimezone=UTC
  spring.datasource.username=root
  spring.datasource.password=your_password
  spring.datasource.driver-class-name=com.mysql.cj.jdbc.Driver
  

  Pay attention to the driver class (MySQL 8+ requires com.mysql.cj.jdbc.Driver, not the old com.mysql.jdbc.Driver) and URL parameters like timezone, which are easy to overlook.

• Database service availability: Confirm your local database server is running (e.g., check MySQL/MariaDB service status via terminal or GUI). If using a remote database, ensure the firewall allows traffic on the database port, and the user account has remote access permissions.

• Dependency conflicts: Check your build file (pom.xml/build.gradle) for conflicting versions of Hibernate, database drivers, or connection pools (like HikariCP). For example, Hibernate 5.6.x works best with MySQL Connector/J 8.0.x—mismatched versions can cause silent connection failures.

• Connection pool exhaustion: If your tests are spawning too many connections without closing them, the pool might run out. Configure your connection pool with reasonable limits (e.g., spring.datasource.hikari.maximum-pool-size=10) and ensure tests properly clean up connections in teardown methods.

• Basic JDBC test: Rule out Hibernate-specific issues by writing a simple JDBC test to connect directly to the database. If this fails, the problem is definitely with your database setup, not Hibernate configuration.

Start with the transaction issue first since it’s consistent across projects—that’s likely to be a configuration or environment fix you can apply universally. Let me know if you uncover more specific details during debugging!

内容的提问来源于stack exchange，提问作者A.heydarabadii