java - Exception when using timeout on transaction - Stack Overflow

admin管理员组

文章数量:1352054

I use Spring Boot 3 with an Oracle database (JpaRepository and Hikari connection are used) and I have a strange behaviour when using timeout on @Transactional. What I want is to do a select but if the query is too long, then I want a timeout with an exception to catch to return a specific error to the front-end.

I use this on the service method:

@Transactional(readOnly = true, timeout = 30)

When timeout occurs, I see these errors in logs:

ORA-01013: user requested cancel of current operation <-- seems to be due to the timeout
...
ERROR o.s.t.i.TransactionInterceptor - Application exception overridden by rollback exception
...
Caused by: oracle.jdbc.OracleDatabaseException: ORA-01013

In the controller, if I catch the Exception thrown by the service, I have a JPA exception (.springframework.orm.jpa.JpaSystemException: Unable to rollback against JDBC Connection) due to the fact that a rollback cannot be done because the connection is closed:

.springframework.orm.jpa.JpaSystemException: Unable to rollback against JDBC Connection
at .springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:341)
at .springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:241)
at .springframework.orm.jpa.JpaTransactionManager.doRollback(JpaTransactionManager.java:593)
...
Caused by: .hibernate.TransactionException: Unable to rollback against JDBC Connection
at .hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.rollback(AbstractLogicalConnectionImplementor.java:137)
at .hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.rollback(JdbcResourceLocalTransactionCoordinatorImpl.java:289)
at .hibernate.engine.transaction.internal.TransactionImpl.rollback(TransactionImpl.java:142)
...
Caused by: java.sql.SQLException: Connection is closed
at com.zaxxer.hikari.pool.ProxyConnection$ClosedConnection.lambda$getClosedConnection$0(ProxyConnection.java:503)
at jdk.proxy3/jdk.proxy3.$Proxy144.rollback(Unknown Source)
at com.zaxxer.hikari.pool.ProxyConnection.rollback(ProxyConnection.java:386)
at com.zaxxer.hikari.pool.HikariProxyConnection.rollback(HikariProxyConnection.java)

I do not understand because my transaction is readOnly so I do not expect to have a commit or a rollback. Also, I do not expect to have an error due to a closed connection but just to have a TransactionTimedOutException or something like that to catch indicating that the error is due to timeout.

I would like to catch an exception in my controller linked to the timeout like this if it is possible to be able to return a specific response to the front-end that there was a timeout:

try {
  this.myService.doService();
} catch(Exception e) { // An explicit exception indication that we had a timeout (ex: TransactionTimedOutException)
  // return a specific error code to front-end
}

For the moment, I have a .springframework.orm.jpa.JpaSystemException: Unable to rollback against JDBC Connection due to the fact that the rollback cannot be done because the connection has been closed after a SQL exception (with ORA-01013 error). I am not able to have information about the original exception that is a SQLTimeoutException.

Can you help me please?

I use Spring Boot 3 with an Oracle database (JpaRepository and Hikari connection are used) and I have a strange behaviour when using timeout on @Transactional. What I want is to do a select but if the query is too long, then I want a timeout with an exception to catch to return a specific error to the front-end.

I use this on the service method:

@Transactional(readOnly = true, timeout = 30)

When timeout occurs, I see these errors in logs:

ORA-01013: user requested cancel of current operation <-- seems to be due to the timeout
...
ERROR o.s.t.i.TransactionInterceptor - Application exception overridden by rollback exception
...
Caused by: oracle.jdbc.OracleDatabaseException: ORA-01013

In the controller, if I catch the Exception thrown by the service, I have a JPA exception (.springframework.orm.jpa.JpaSystemException: Unable to rollback against JDBC Connection) due to the fact that a rollback cannot be done because the connection is closed:

.springframework.orm.jpa.JpaSystemException: Unable to rollback against JDBC Connection
at .springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:341)
at .springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:241)
at .springframework.orm.jpa.JpaTransactionManager.doRollback(JpaTransactionManager.java:593)
...
Caused by: .hibernate.TransactionException: Unable to rollback against JDBC Connection
at .hibernate.resource.jdbc.internal.AbstractLogicalConnectionImplementor.rollback(AbstractLogicalConnectionImplementor.java:137)
at .hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.rollback(JdbcResourceLocalTransactionCoordinatorImpl.java:289)
at .hibernate.engine.transaction.internal.TransactionImpl.rollback(TransactionImpl.java:142)
...
Caused by: java.sql.SQLException: Connection is closed
at com.zaxxer.hikari.pool.ProxyConnection$ClosedConnection.lambda$getClosedConnection$0(ProxyConnection.java:503)
at jdk.proxy3/jdk.proxy3.$Proxy144.rollback(Unknown Source)
at com.zaxxer.hikari.pool.ProxyConnection.rollback(ProxyConnection.java:386)
at com.zaxxer.hikari.pool.HikariProxyConnection.rollback(HikariProxyConnection.java)

I do not understand because my transaction is readOnly so I do not expect to have a commit or a rollback. Also, I do not expect to have an error due to a closed connection but just to have a TransactionTimedOutException or something like that to catch indicating that the error is due to timeout.

I would like to catch an exception in my controller linked to the timeout like this if it is possible to be able to return a specific response to the front-end that there was a timeout:

try {
  this.myService.doService();
} catch(Exception e) { // An explicit exception indication that we had a timeout (ex: TransactionTimedOutException)
  // return a specific error code to front-end
}

For the moment, I have a .springframework.orm.jpa.JpaSystemException: Unable to rollback against JDBC Connection due to the fact that the rollback cannot be done because the connection has been closed after a SQL exception (with ORA-01013 error). I am not able to have information about the original exception that is a SQLTimeoutException.

Can you help me please?

• java
• spring
• spring-boot

Share Improve this question Follow edited 2 days ago phildeg31 asked Apr 1 at 13:06 phildeg31phildeg31 26955 silver badges1919 bronze badges 1

• Since spring JPARepository intercept database exceptions and replaces it with their own the correct approach for you is to write your own interceptor for it. Something that is discussed here: stackoverflow/q/69646662/460557 – Je Campos Commented Apr 1 at 21:11

Add a comment  | 

2 Answers 2

Sorted by: Reset to default 0

As far as I'm concern, any transational query is handled by Spring Boot's TransactionManager, which is the one doing the rollback that causes the exception, even if it is a readOnly operation.

If you're only concerned about the actual read, maybe you could just use @Query or @QueryTimeout headers with setHint. Or even set the default read timeout to whichever value you need using spring.datasource.hikari.dataSourceProperties: oracle.jdbc.ReadTimeout=XXX

Hope this helps!

I'm a little unsure I understand the question exactly but I'll put out a couple of leads to follow. Maybe add more information to your question if these suggestions aren't helpful.

1. "Application exception overridden by rollback exception" means that the exception you catch should have a "suppressed" exception connected to it. That "suppressed" exception is the application error that prompted the rollback. Inspecting the suppressed exception using getSuppressed might help you solve the root problem.
2. If your connection is being closed before the timeout occurs, this should be fixable by tweaking your DB connection configuration details. Ensure that the connection timeout is higher than the timeout of any query. (Check this configuration on the Oracle side as well since those Oracle setting supersede anything you do on your application side.)

本文标签： javaException when using timeout on transactionStack Overflow